rubs

I've recently used the contour effect. It's great, but unfortunately it crashes too often when editing multiple grouped objects at the same time.

I believe the BMP format is pretty obsolete for many years now so I understand if Serif chooses not to implement an export filter. I use Inno Setup too, but it's the only dev tool I use that still does not accept PNGs AFAIK. The task runner / ImageMagick idea is the best idea for continuous export, but for sporadic use the venerable IrfanView is great. It is super fast, can import / export hundreds of bitmap formats, has a command-line interface and batch options and is completely free (Windows only, sorry).

This is great news, Ben. Looking forward to seeing some nasty bugs fixed too.

I understand the feeling, in the very beginning I also found this behavior quite strange and I thought it was a bug. But now I'm used to it and I can see the benefit of easily experimenting with blending, adjustments, effects and so on, especially when you have many layers. Just select the objects you want and apply the effect. If it's not right, then undo -- it will keep the selection -- then try another one. This feature is unique to Affinity Designer, I really like it.

Thanks for listening, and thanks for your answer. AD is my main design tool, I use it on a daily basis. I'm a big advocate of it among fellow designers, and I've already produced hundreds (thousands?) of work files with it. So I'm not going anywhere soon But I feel it's important to know whether these showstoppers will be addressed or not (and when), but I'm not seeing any answers. Please look here for more thoughts. Thanks again.

By now I assume they are not bothering with this problem and many other serious bugs that were reported a long time ago. They are too busy developing new products..

So far, so good. No crashes yet! Fingers crossed.

Will do, thanks!

There are no real differences between the two versions. Technically, Affinity software is always beta because it has hundreds of known bugs. So I tend to use the latest version available, keeping an eye on new bugs.

Good news. Hope you nail it this time. I'll keep an eye on the news for the new beta. Thanks!

For me it happens even with small (< 1 MB) files, but those files have lots (thousands) of vector objects and several artboards.

Just happened again, sent the crash report. Pleas also look at this post for more.

I don't know the reference number. Is there a way to know it? The folder %appdata%\Affinity\Designer\1.0 (Beta)\CrashReports is empty. It was sent just a couple of minutes before my posts. My email starts with "pechansky".

...and again. Please tell us you'll fix this in the next beta . Any answers are welcome.

Right now I've just crashed AD while moving artboards around. I just sent the bug report. I can send you the offending file if you want.

When resuming from hibernation, AD crashed. Same thing as yesterday morning. Just sent the crash report. Anyone else has this?

Understood. Anyway the idea would be to mark only the key object inside the selection, not the selection itself. Marking the selection would make sense for symbols only. And I'd love to hear from @MattP about a way to show symbols in the main area.

Great, thanks for the info.

For me, marking special objects would more useful than defining layer colors, but I understand there are many users that love being able to change layer colors. Just for reference, below I show the symbol Xara Designer uses to mark objects that repeat on all pages. As for the key object, maybe adding small symbols like this would be a solution. I'm sure there must be a way. Thanks again.

This is a really annoying bug. Will you fix this for the next beta? Please?

I think using the selection color and line styles (or other visual indicators in the selection) would be great for this and other uses. See here for a related idea concerning using the selection color for symbols:

My company and I use CorelDRAW 15 (X5) on Windows 10. I remember we had to do some hacks to make the menus visible, but that was about it.

In the latest beta (I never noticed it before), pressing Esc in the Text Height field in the context toolbar does not take you back to the working area. The control goes blank instead. Pressing Esc again brings the current value back, and so on. Please take a look at this -- thanks.

Yep, same thing in the Windows version as expected. This bug was recently introduced by the devs and was already reported a while ago, but unfortunately nothing was done to fix it so far.

Any hopes here?