Ramon0

Well, everything has already been said/argued... So just another simple: +1

Hi. Incredible list of solved issues! And I'm happy to see that you finally addressed the Symbols & Booleans issue I was referring here some revisions ago since everything regarding that seems to behave as expected now. Well thank you very much! I'm definitely in love with both (terrific) features and it's great to see them work well together at last :D ...Greetings and thanks again!

Those are a lot of fixes, thank you! I reported a bug in the thread for 1.5.0.10 that has not been fixed yet, though. It's all about Symbols and booleans not working well together (a very serious issue I'd say) and you have all the details here: https://forum.affinity.serif.com/index.php?/topic/23375-affinity-designer-public-beta-15010-windows&p=110155 But the thing is that, at this point, I'm not even sure if developers are really aware of it... so any confirmation about it would help. OTOH, if you simply prefer bugs like this be reported separately or something, I'm all hears about those aspects as well. Thank you and I hope it helps.

Hi and, first of all, thank you for the new update. I've a doubt, tho... In the previous version's announcement thread, I reported the following bug related to booleans and symbols: https://forum.affinity.serif.com/index.php?/topic/23375-affinity-designer-public-beta-15010-windows/&p=10155 But it turns out it's still happening here in v1.5.0.11, so I'm not sure if it's been taken into account or passed unnoticed... Are you aware of it? Or would have been better if I'd reported it in any other way? Of course, I still could do it if necessary... Well, that's all for now. Thanks in advance for any attention and greetings!

Thank you very much for a so quick new update and very specially for emphasize about performance. I've found a problem related to symbols and booleans, tho... It's simple, if I create a simple nondestructive boolean and I make a symbol of the resulting "Compound" object, instances don't get updated in viewport when you make changes like translate points, etc, while for simple symbols not containing any booleans at all, changes are propagated instantly and as expected. Also, I've been getting some crashes while manipulating this kind of objects and/or their symbols that I'd say well could be related (one crash report at least, the one I obtained while saving, has been already sent to you by means of the application when asked). I could attach a simple sample file if needed. BTW... is there a preferred way to make attachments here? I thought I could directly upload them by means of some forum functionality, but I'm not able to find it yet * ...Anyway, I hope it helps and greetings! * OK, I figured it out :), so there it is the try me... Just create a symbol based on the Compound object and then insert it anywhere. Select the "Node Tool" and start translating some points or handles of the original. You'll see how changes are not real-time propagated, even the "Sync" button is (of course) pressed. AD1.5.0.10W_symbols-&-booleans_20160806-0239_try-me.afdesign

Thank you! No problems so far but quite the contrary. Besides stability, it's like performance is also improving more and more and that's something me and my Core 2 Duo CPU really appreciate :). Well, keep up the excellent work and thanks again!