Archangel
-
Posts
355 -
Joined
-
Last visited
Posts posted by Archangel
-
-
Okay, I would like to add support for this feature.
Check out the Mirrored publisher file for a possible future workaround.
-
18 hours ago, v_kyr said:
Sounds promising so far, let's hope it remains at this working state also after the next MS Win updates.
I'm waiting for V2 to appear now. Hopefully with Footnotes, Endnotes and Side Notes, Auto Trace, Story Editor, Photo management, and Grammar Checker thrown in. Still, we'll have to wait and see.
-
On 6/1/2022 at 9:33 AM, stokerg said:
The crash reports don't really tell us a great deal about why the app is crashing, other than the crash is in KERNALBASE.DLL
So we can work out just when the crash is happening, if you open Affinity and close it, make a note of the time and check the crash reports folder is there a new report with same time as when you closed the app?
The latest .NET cumulative preview update seems to have sorted the issue. I'll let you know if it returns.
-
45 minutes ago, v_kyr said:
Then look instead through Windows system Affinity apps related crash & error logs (Windows Event Viewer & Reliability Monitor) ...
... maybe you see there then some additional indications for what might went wrong (why Affinity crashes) during app closings etc.
Tried both but nothing showing regarding Affinity apps.
-
51 minutes ago, v_kyr said:
As I'm personally not on a Win system (instead running MacOS) you would have to go through and analyze that PML file on your Win system via Process Monitor then.
It doesn't tell me a lot. Except that a lot of files are locked for reading and certain keys in Internet Explorer are not found.
-
Yep, here is the latest DMP. Matches time exactly. Also included a Process Monitor log from a later run and crash.
20c1e5e5-cf11-4450-a98a-fb14abdb914b.dmp Logfile.PML c04a30da-8a94-4519-a727-a9724ea3fa28.dmp
-
1 hour ago, stokerg said:
The crash reports don't really tell us a great deal about why the app is crashing, other than the crash is in KERNALBASE.DLL
So we can work out just when the crash is happening, if you open Affinity and close it, make a note of the time and check the crash reports folder is there a new report with same time as when you closed the app?
I noticed that happened last night when I closed the app the time matched the crash report exactly. Yes, all I have to do is open and close the app to generate a new crash report that matches the time of closure.
-
24 minutes ago, v_kyr said:
Good point, ... then one has to find out what one of the last tasks is the Affinity apps usually do during closing, like for example writing/updating some settings which then probably are never stored/set during the shutdown/closing process.
Definitely one for the programmers.
-
22 minutes ago, walt.farrell said:
It could be crashing during the process of Closing. You're expecting the UI to go away, and it does, so you don't realize anything is wrong.
Very possibly. I hope the Serif team will take a look at these files at some point as my ssd will slowly fill up with them. It was only due to OO Defrag reporting new fie fragmentation that I noticed them in the first place. Although, Privazer will delete them.
-
1 hour ago, v_kyr said:
Those for Designer (only looked into two of them from today) always tell ...
And those from Publisher then pretty much the same ...
I see sometimes there Mscoree.dll among the stack traces which AFAIK is a MS browser extension for Internet Explorer.
Checking those DLLs, they appear to be part of the Microsoft .NET framework version 4. I tried repairing the framework, but the crash report still occurs despite the app closing normally. Thanks anyway.
Photo does the same.
-
1 hour ago, v_kyr said:
What are the date & timestamps of those crash files and what do they contents wise tell?
I don't know how to read them. Here is a zip with the crash dumps from publisher and designer.
-
Bizzarely, both Publisher and Designer create a lot of crash dump files even though I haven't experienced any crashes but just close the apps normally.
Anyone know why this happens?
This is on Windows 10 64 bit.
-
I have created some Autotrace vector assets based upon free images and my own images. They are an assorted mixture, but may be useful for some people.
The uncompressed file is quite large, so I uploaded a 7z archive.
Sample JPG included.
-
On 12/16/2020 at 6:14 PM, Patrick Connor said:
This is is simply an incorrect understanding. The same team who wrote PagePlus are writing Affinity Publisher. These programmers can access the legacy code (if desired), but there is no need, they wrote it and know how they wrote it. Legacy code and the Affinity code is not shared as the implementation and architecture are not similar. This feature needs writing using the current language spec and using the current OS independent architecture and algorithms. Code like this is not simply plug and play
True. Algorithms my travel and improve between architectures, but code will not. At least not easily.
-
Nice. Welcome to Affinity!
-
My export feature keeps defaulting to the Sytem32 folder, which is annoying but easy to work around. Export defaulting to a system folder is a little crazy
.
-
With the final closing of Community Plus for Serif's legacy products, I thought I'd create something to remember that range.
Goodbye Old Friends.
DrawPlus X8 was used to create the background SVG.
Included the package for you to mess with.
The rest of the work done in Affinity Designer.
-
On 6/6/2019 at 8:50 PM, v_kyr said:
Related to the overall fruitless scripting debate here, it doesn't matter what sort of language finally would be used, as far as the chosen one is powerful and fast enough to express the kind of things and algorithms people have in mind to build for the tools. So more important is to map a rich reusable set of the internal functions into that language then and also offer integration hooks into the UI.
It also should be a secure language to prevent security issues and malware attacks.
-
Here is a poem I created and laid out in Affinity Publisher. An early example of the use of a background style watermark effect.
A very simple layout but quite effective.
The zip file contains the Affinity Package for people to play with.
Michael
- The Letter M and dannyg9
-
1
-
1
-
Reminds me of the Fuzzy Felt we used at Primary School. Sterling work.
-
On 9/6/2021 at 5:08 PM, R C-R said:
FWIW, several years ago one of (I think) the developers said they would not implement auto tracing unless they could improve on what is (or was at that time) already available in other auto-tracers.
What that means is anybody's guess.
Fascinating. It's a shame as their DrawPlus application had an excellent autotrace function. Example loaded.
-
Serif already had a very good autotrace function in their DrawPlus application. One wonders why they couldn't optimize the code and adapt it to their designer application.
-
1 hour ago, philippe martin said:
Hi,
I was amazed when I got Rebelle 5 and its new pigment mode.
I then discovered a few days ago that Affinity Photo already had that feature - unless I am missing something obvious.
Ex:
1) take an oil brush (Impressionist Oil works pretty well)
2) set tool as mixer brush
3) make sure mode is "YRB"
4) Pure blue + pure yellow will yield green.
A game changer to me.
Regards,
Philippe
Subtractive colour models are an improvement but the new technique allows for simulation of pigments and their textures in real paints giving it the edge
-
Until we get a story editor in Affinity Publisher, here is an option for Windows Users. The full version is now free to all. This could be a useful lightweight word processor which may cater to our needs. Sadly, it is no longer being developed, but it is worth a look.
Why are there so many crash dump files in Affinity Data?
in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Posted
Okay, the Publisher crashing is back on closing.
2c4fe3e3-3d66-4609-b7b1-44bb93eeb538.dmp