Jump to content
You must now use your email address to sign in [click for more info] ×

1.8.0.502 crashes after placing bigger .afdesign file, also text styles


Recommended Posts

I know I shouldn't really do this, but after experimenting with the pub18-502 beta and its amazing idml import, I decided to jump into the cold water and use the beta for a small but urgent project (today) in real-life. This way you actually see all shortcomings because you highly depend on it to function correctly.

So my Problem is with placed .afdesign files. I have 8 afdesign-Icons linked in my one-page document. Also, there are some text-styles imported via idml which also have weird anomalies*

At some point I opened the triangle in the layers panel and it immediately showed the beach ball followed by the crash report.

Then, after recovery and redoing the lost part of the work, I imported another, highly complex .afdesign file into publisher and after maybe ten clicks same crash again.

So I want to report this here and in the meantime I will refrain from importing this AFDesign file again and instead convert it to pdf or so...

 

*text style anomalies:

when changing one of two hierarchical textstyles, the other one changes the font-weight. The problem is a combination of the font Helvetica Neue LT which has many font weights combined with publishers style preferences, which differentiate between FONT WEIGHT and FONT TRAITS. My Helveticas weights are listed as Traits. And secondly, the default style is not Roman or Book but "Condensed Light"... which is also bad...

 

1285375427_Bildschirmfoto2019-11-20um11_24_43.thumb.png.d8a2471655d8b01638b0b40d7b7c2852.png1867033722_Bildschirmfoto2019-11-20um11_24_58.thumb.png.e52011660434f9fce9ac53ace128a027.png

 

  • Main machine: iMac 2019 (21,5-inch 4k, 6core), 64GB RAM, 1TB nvme + 2TB ssd, running on Mac OS 13;
  • Display setup: 28" 5k Display (primary) + 21,5" iMac4k-Display for studio panels (secondary);
  • Keyboard layout: german apple extended keyboard (aluminium);

 

Link to comment
Share on other sites

  • 4 months later...
  • Staff

Sorry.

Thank you for reporting a problem using the pre 1.8.0 beta builds. It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. 

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the release build.

Patrick Connor
Serif Europe Ltd

"There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self."  W. L. Sheldon

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.