TonyB

We will support a very limited set of platform specific automation functions with one of those exposed functions being able to pass a Javascript snippet that will then have full access to Affinity. Hope that makes sense.

Affinity will support Javascript and also have a 'C' based API binding interface that people can use to write plugins. We will also have the ability to create UI to support their scripts and plugins with dialogs and panels. We have a team developing this but the amount of work is very large so unfortunately users will need to be patient.

Thanks for all the feedback so far it has been very helpful. So currently the decided points are as follows; We introduce a new parent only layer type called a Global Layer All Global Layers are added to all spreads and Master Pages All visibility and ordering is controlled globally Pages are rendered in Global Layer order across spreads and master pages Normal layers still exist but are children of Global Layers If you don't use Global Layers then they will not be shown in the Layers panel No point really discussing the points above as they are now decided and I would like to narrow the scope of this discussion to undecided things. So still to be decided; What happens to existing documents Should existing Master Pages be converted into a new Linked Spread and would this feature be useful for other things Should Master Page items be visible in the Layer panel for the current spread Should we replace multiple master pages per spread with Master Pages that can inherit from other Master Pages Should Global Layers be the default for Publisher Discuss...

Do you think we need Global Layer previews in the Layers Panel? I think it would look simpler and cleaner without.

I agree but you could move the Master-A parent node up and down scoped within the specific Spread Global Layer without any major issues. I think the bigger question is whether seeing the Master-A node within the current Spread would confuse people as it will only show the objects from the same Global Layer that they are expanded within.

So let's imagine I agree, how should it work within Affinity? We add a new parent layer type called Global Layer and it should be the default type for Publisher. When you add Global Layers they are added to all Spreads and Master Pages When you hide, show, colour tag or re-order, it will happen across all Spreads and Master Pages Easy so far. When you apply a Master Page (Master-A) to a Spread then what would you see in the Layer Panel when that Spread is selected? It should show nothing ever. When you expand a Global layer It should show Master-A for the corresponding Global Layer. As above but only show Master-A if the Master Page has items on the corresponding Global Layer. Something different. If you choose 2 or 3 then you could still select the items and even drag the Master-A parent above your Spread items to change Z order within your Spread items. Discuss...

I'm just adding my weight to the request

It's not hard and I agree the light UI in system dialogs when the OS is in light mode is much nicer.

A 4K monitor should have a high scale setting in Windows. If the other applications don't work at the scale then they are to blame for not working properly in Windows. How big is your monitor? I have an iMac 5K 27 inch so macOS will be @200% scale and everything is fine. All our icons are already high resolution so we can display them at different scales. What colour they are is a different discussion.

if you are running at 200% scale then you are still using every pixel on your new monitor. We just use bigger assets for icons, buttons etc. If you do a screen grab of your old monitor @100% and then you new monitor @200% and compare, you will find it has double the resolution.

How about Affinity supporting AppleScript but only for for coarse grained functions with execute JavaScript snippet as one of those functions?

It's not that much work for us to recompile for ARM64 as we already do it for iPad. The problem is Microsoft has thrown us under a bus by not supporting WPF on ARM64. All 64bit applications that use WPF will have the same problem porting to ARM64.

Agreed, this needs fixing. Thanks, TonyB

The main problem is Affinity runs on a 64bit architecture but Windows on ARM doesn't support 64bit WPF that we use for our UI. We would need to rewrite the entire UI to target Windows on ARM.

Sorry but there isn't currently a way of closing a shape on creation when using the Pencil tool. You can however close the shape using sculpt after. This will be improved in a future update.