LCamachoDesign

Bumping this topic up to the top. This issue is unsolved and still happening in all 1.8.3 Affinity apps.

This is fixed in all Affinity apps now. Thanks!

If the option "Use Windows Ink for tablet input" is enabled, any jitter happening when tapping the tablet with the pen will be detected as a mouse drag instead of just a click, regardless of how small our hand/finger movement is.
The most obvious consequence of this issue is this bug previously reported here:
But it actually completely breaks the whole app workflow, since any selection you do with the pen will register both as a selection and also a move, flooding the History panel at twice the rate. It will also literally move any object by tiny amounts, breaking all alignments you may try to do. Have a look at the attached video. I'm illustrating the issue in Affinity Designer here, but this happens in all Affinity apps.
There should be a threshold of pen movement to register as an actual move object request, anything below that should be considered a tap. Until this is fixed the only way to use these apps is disabling the Windows Ink option.
Additional information:
I'm using Windows 10 18363.720 Wacom drivers are 6.3.38-2 Tablet is a Wacom Intuos CTL-480/S The "Use Windows Ink for tablet input" should have a "(requires restart)" warning BTW Thanks!

recordedVideo.mp4

If the option "Use Windows Ink for tablet input" is enabled, any jitter happening when tapping the tablet with the pen will be detected as a mouse drag instead of just a click, regardless of how small our hand/finger movement is.
The most obvious consequence of this issue is this bug previously reported here:
But it actually completely breaks the whole app workflow, since any selection you do with the pen will register both as a selection and also a move, flooding the History panel at twice the rate. It will also literally move any object by tiny amounts, breaking all alignments you may try to do. Have a look at the attached video. I'm illustrating the issue in Affinity Designer here, but this happens in all Affinity apps.
There should be a threshold of pen movement to register as an actual move object request, anything below that should be considered a tap. Until this is fixed the only way to use these apps is disabling the Windows Ink option.
Additional information:
I'm using Windows 10 18363.720 Wacom drivers are 6.3.38-2 Tablet is a Wacom Intuos CTL-480/S The "Use Windows Ink for tablet input" should have a "(requires restart)" warning BTW Thanks!

recordedVideo.mp4

Can confirm this does fix the issue, however, disabling this setting on a Microsoft Surface disables the touch gestures as well so its definitely as band-aid solution. I'll be testing this out on my Cintiq as well when I'm home from work.
Here's hoping this gets fixed soon!

It's what the title says, ability to see markers for tabs, paragraph markers, spaces, line breaks, and so on. Absolutely fundamental for any kind of design using more than a couple of line of text.
Thanks!

Hi @LCamachoDesign,
Thanks. I logged this with our developers. 

Totally agree. For me that i used mainly on iPad is really important that the swatch panel change. Just a few changes will make more effective.
A search field for example when navigating in the swatches panel like pantone for example. Otherwise you have to scroll through all the colours.
I love Affinity app and I'm happy were things are going. I think the only suggestion I can give is to keep up with the speed of update. The app world is change and people will change so quickly if they don't get what they looking for and it would be a disaster in my opinion if we will love Affinity apps during the journey. They add competition in the market but the market is also so unstable in the recent here. 
Anyway. I'm always on Affinity side just because the gave me a chance to choose and to choose something that makes me productive.
But of course i fell there are still a lot of things to improve to the iPad. At least to give us the same features of the desktop.
M

+1 on the ability to create, use and modify global colours.
I've recently got a hold of an iPad and discovered this issue. Kind of a show stopper since I use them extensively... I also noticed you can't use swatches, even the normal kind, in layer effects such as Colour Overlay...
I honestly think the swatches panel needs a big overhaul, both desktop and iPad. I mean just have a look at the how the Swatches panel works on Illustrator and copy it, then sprinkle a bit of InDesign features into it and you have a perfect panel. No need to reinvent the wheel.
I'm always puzzled on how these things happen, Adobe's swatches panels are widely known, there's no way the team didn't know them. It's almost like they decide on a meeting that "we know these panels works great, so instead let's make something similar, but that works worse!" 

You have to be kidding me... it does work! The performance goes back to Photo levels, and it also solves the first stroke delay after zooming I reported in the other topic. Thank you!
This solution would have never crossed my mind... this does happen frequently with Affinity applications though. More than once I come across "issues" for which the solutions are already on the app, they're just sort of hidden away. 
 
For this situation I think a UX tweak would help users a lot, especially in lower performance devices.
First there should be an application-wide option saying something like this: "Change view modes to match the Persona"
This option would work like this:
If in Designer Persona Then View Mode is Vector Else If in Pixel Persona If Document Type is Devices (Retina) Then View Mode is Retina Pixel Else View Mode is Pixel End If Else If in Export Persona I'm not quite sure? Perhaps Vector view mode again? Or Retina Pixel if the document is Devices (Retina)? End If Then, upon the first time a user switches to the Pixel Persona a popup or something should ask the user if they'd like to enable this option for a more accurate preview of the pixel artwork and enhanced performance.
 
Another alternative would be to have an option to make the view modes sticky in regards to the persona being used. So if I change the view mode on the Pixel Persona to Pixel, then it will always change to that whenever I return to that Persona on that document. If I set the view mode to Vector in the Designer Persona, then it will change to that mode whenever I return to it. This way you can seamlessly switch between high precision vectors and high performance pixel whenever needed.
I still think the performance difference is so large that by default Designer Persona should be Vector view, and Pixel Persona should be pixel view. Let the user change it if they want, but let this be the out of box experience so the optimal performance is not hidden away! You can say my iPad is old, which is very true, and on a brand new 3rd gen iPad Pro you can barely tell the difference (not sure if that's the case, but let's go with it). The thing is Apple keeps selling iPads with low processor power even right now, so this is not an issue that will go away on it's own anytime soon. Implementing something along this lines will help these people achieve maximum performance on their brand new, albeit slower, iPads.
 
Thanks!

I'm glad that worked. I moved this to feature requests

Hi @LCamachoDesign
This is kind of expected, because of the different rendering engine. In Photo, it would only render what's on-screen at that zoom level. So, if your image let's say it's made of 50tiles, when you're zoomed in 10x, it will only render that tiled portion, so 5 tiles.
 However, in designer, being a vector renderer by default, it redraws all the tiles regardless of the zoom level, when using the "Vector" View mode. Chaing the View mode to "Pixels" should give you a similar result to what you see in Photo. Give it a go and let us know how it goes.

Hello guys,
I also searched for this feature today.
»Saved« under »Document Statistics« comes closest, because you probably save
the document as soon as you make changes.
However, if you only open the document to export it as a PDF and don't make any
changes, a field that updates itself as soon as you open it might be handy.
In fact, I assumed »Date & Time« would be this field, but it's static and takes
only the date at the time you insert it.
Greetings
MrDoodlezz

Ability to apply colour swatches to layer effects, such as the pictured Colour Overlay. Right now you can only use sliders and wheels on these.
This is particular useful when used in conjunction with global colours. You can apply a global colour to a large number of layer effects, and change every single of them instance just by editing the global colour. I use this a lot in illustration, rather than paint any drawing in it's 'final colour', I have the brush set to black and the layer with a colour overlay effect attached to a global colour. If I later want to change the illustration colour I just edit the swatch.
Thanks!

We are aware of a very small delay after panning/zooming. 

I've had a project where I've had to use Place to place a lot of images (basically setting up a deck of cards in Publisher to go to print). Every once in a while, after using the menu to click on Place, the area where you select document type gets set to TXT instead of ALL. I never change this, so the software is doing it on its own. It does not happen every time, but it does happen frequently - maybe once every four or five times accessing Place. 
BTW - This happens in both Publisher and Designer. I've not tested this in Photo.

I find the fields feature to be very useful, but it would also be useful to be able to be able to define your own custom fields.

Hello there! I can confirm the app gets unbearably unstable (freezing, unable to zoom/move) when using specifically the Clone Tool too much. I mean, if you’re just going to clone certain part of a photo, it makes no difference; but, if you’re doing some serious cloning for more than 5-10 minutes, the app just freezes and prevents you from selecting other tools. It also affects panning and zooming using gestures.
It happens 95% of the times to me. I’m using a 12” iPad Pro 2018.
- Enrique 

Hello all,
I'm sorry you've been having these issues. We know of an issue where doing the five-finger pinch gesture to return to the Home screen can cause the app to severely lag when you return to it. If this is the gesture you commonly use, please give it a go and let me know.
I've also been informed by a colleague that there can be a severe delay (approx 5 secs) between putting the Apple Pencil on the screen to draw and it appearing. This can happen on a document as small as 4000 px x 4000 px in RGB8 and 16. That was reported against a 9.7 pro (2016). 
@frankthechicken - I have just created a 16000x8000 px document on 1.7 and can indeed reproduce this. I then made the same size document on an older iPad running 1.6 and saw no such delay. I will speak with dev. 

If this is what I think it is, then THANKS. As a new user, the lack of this working before caused me grief.

I've searched around and while I see people asking about this, doesn't seem like there's any kind of formal request for this feature so here's one.
Essentially it's what the title says, please add the ability to create, edit and apply global colour swatches in illustrations and designs done on the iPad. Global colours are a fundamental part of vector design and illustration, the need for this is vital!
Right now the only workaround is to create them on the desktop and then open the file on the iPad, but this has limitations besides not being able to edit the swatches on the device itself. For example if you apply a global to an object, the swatches panel will not indicate in any way that the colour is apply to the object, unlike in the desktop where you can see the swatch highlighted.
Thanks!

Hi @LCamachoDesign,
Sorry for the delayed reply. I've logged this with our developers.
Thanks,
Gabe. 

If you change the displayed/active artboard of a multi artboard Designer file placed on a master page, this change won't be reflected on regular pages. It always shows the artboard that was first visible upon placing the file. It's possible this also happens with other types of multipage documents (Affinity Photo, PDFs) but I only tested with Designer files.
 
Steps to reproduce:
Open Affinity Designer Create a new document with 2 Artboards Draw a purple circle on the first artboard and a blue square in the second, just so they're instantly recognizable Save it somewhere, you can now close Designer, it won't be used anymore Create a new Publisher file, check Default Master so a master page is already applied to any pages added Add a few pages to the document, let's say 6, just so the issue is more evident Double click Master A in the Pages panel so you can add elements to it Place the Designer document you saved on step 4, by default it should show the first artboard, the purple circle Notice the purple circle is correctly displayed on all pages where the Master A is applied Back on the Master A, select the placed file and use the context toolbar to change to the second artboard You should now see the blue square on the master page as expected Notice that the blue square is not being shown on the pages where the master is applied, instead you continue to see the purple circle This is not just a visual bug, if you export a PDF all pages will indeed have the purple circle instead of the blue square  
Thanks!

I'm a little late to the party (I had not tested the beta versions since I'd commented.)
Thank you Affinity Dev Group! The pen feature is working absolutely perfect now.
-Ryan

It's hard to blame it on particular authoring programs. PDFs are notorious in general for containing unexpected clipping paths, even when exported and imported using Adobe apps. As constructs native to the authoring program get "deconstructed" down to more basic objects, anything from grad fills (beyond the basic linear and radial) to mere page bounds can result in clipping paths—even multiple nested ones—when exported to PDF.
It's one of the reasons why Illustrator has its specific Select>Object>Clipping Masks command. All the dubious hype about "Illustrator's native format is now PDF!" lead users to think that's true in a conventional sense. So they use Illustrator to "open" PDFs from any willy-nilly source (not just the ones created by Illustrator with its "Maintain editability..." option turned on), and encounter all those clipping paths, too. So it's common practice in Illustrator to just select that command and hit delete, in order to figure out what you're actually dealing with.
JET