-
Posts
1,617 -
Joined
Everything posted by TonyB
-
Try three finger swipe down. I think you might be pleased.
-
There isn't any scripting support in V2 yet. We have a dedicated scripting team here typing very quickly but still no definite timeline for release yet.
- 581 replies
-
- automation
- scripting
-
(and 3 more)
Tagged with:
-
Global layers
TonyB replied to Tony Cotterill's topic in Feedback for Affinity Publisher V1 on Desktop
It's a big piece of work that requires major reworking of rendering and DOM structure. It will happen but will take time. It's high on our internal feature board. -
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.
- 581 replies
-
- automation
- scripting
-
(and 3 more)
Tagged with:
-
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.
- 581 replies
-
- automation
- scripting
-
(and 3 more)
Tagged with:
-
Global layers
TonyB replied to Tony Cotterill's topic in Feedback for Affinity Publisher V1 on Desktop
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... -
Global layers
TonyB replied to Tony Cotterill's topic in Feedback for Affinity Publisher V1 on Desktop
Do you think we need Global Layer previews in the Layers Panel? I think it would look simpler and cleaner without. -
Global layers
TonyB replied to Tony Cotterill's topic in Feedback for Affinity Publisher V1 on Desktop
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. -
Global layers
TonyB replied to Tony Cotterill's topic in Feedback for Affinity Publisher V1 on Desktop
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... -
Dark UI for Photo but light save/open finder window
TonyB replied to Mr Lucky's topic in V1 Bugs found on macOS
I'm just adding my weight to the request -
Dark UI for Photo but light save/open finder window
TonyB replied to Mr Lucky's topic in V1 Bugs found on macOS
It's not hard and I agree the light UI in system dialogs when the OS is in light mode is much nicer. -
pdf export rasterises simple shape
TonyB replied to woefi's topic in [ARCHIVE] Publisher beta on macOS threads
This is very true for newer PDF versions. This should be an improvement request. -
UI too small
TonyB replied to mr.burns's topic in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
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. -
UI too small
TonyB replied to mr.burns's topic in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
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?
- 581 replies
-
- automation
- scripting
-
(and 3 more)
Tagged with:
-
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.
-
Pixel tool creates jaggy lines when shift-clicking
TonyB replied to antonkudin's topic in V1 Bugs found on macOS
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.
-
With a facing page document, then this is expected. If you have content that goes across spread and it will be printed as a booklet/book then this is fine as the printer will impose the pages with the inner bleed removed. If you don't need to have content that goes across the facing spread (both left and right pages) then switch the document type to non facing.
-
Website failure cannot pay
TonyB replied to Roger terry's topic in Customer Service, Accounts and Purchasing
The website should be working again now. Sorry for an inconvenience. -
Switch from MAS to Infinity Store
TonyB replied to Pebowski's topic in Customer Service, Accounts and Purchasing
Unfortunately converting Mac AppStore sales into external store sales is against Apple rules and we would be thrown off the Mac AppStore if we did it. Sketch did let you convert and hence they came off the App Store.