scrolling problem after upgrade

[dizeyner]

for the second time on upgrading my affinity products the upgrade has introduced a scrolling bug. last time I had to reset SMC to get it to stop but last time it just affected affinity. this time right after upgrading last night ANYTHING that scrolls has gone wacko. leaving me to believe affinity has introduced a bug or a virus to my computer. I hope this is not the case but I do find it strange that this is happening only when affinity apps get updated on my imac.

[R C-R]

It might help if you explained in more what it is that goes "wacko."

[Dan C]

Hi dizeyner

I'm sorry to hear you're having issues after updating. If you could please provide a screen recording of the issue then I'm sure we can help here.

If you wish, you can try resetting the app back to default settings, you can reset your app back to its default settings by holding down the CTRL key while launching the app. When the Clear User Data window appears, click Select All and then Clear. The app will now open.
Be aware that resetting your app back to its default settings will lose any custom settings such as keyboard shortcuts and brushes etc. To backup such settings before resetting the app, please watch our Affinity - Exporting User Settings and Keyboard Shortcuts video. https://vimeo.com/189596577 

[R C-R]

26 minutes ago, Dan C said:

Be aware that resetting your app back to its default settings will lose any custom settings such as keyboard shortcuts and brushes etc To backup such settings before resetting the app, please watch our Affinity - Exporting User Settings and Keyboard Shortcuts video.

A bit off-topic but I hope that someday the apps can provide a way to do all the backups in one step, perhaps placing each kind in individual subfolders, because it is really tedious to do all of them individually, one at a time.

[Dan C]

21 minutes ago, R C-R said:

I hope that someday the apps can provide a way to do all the backups in one step

This certainly would be nice, I'll make sure there's an improvement logged for this, but I'm pretty sure there is