shushustorm

Hey everyone! When I set a layer's opacity to 50%, then slide to the right to 100%, then try to undo, it won't work. I am using Designer 1.10.4, which may not be the most current version. I am rarely updating in order to keep workflow stability. I searched for "slider undo" and didn't find this issue. Best wishes, Shu

Hey everyone! When typing "10" for opacity, I am always getting "100%" rather than "10%". 5 becomes 50, I think, as well. Not sure this is an OS issue, I'm on a Mac, using Designer 1.10.4, which may not be the most current version. I am rarely updating in order to keep workflow stability. I searched for "picker 10" and didn't find this issue. Best wishes, Shu

Hey everyone! Is there a way to keep an objects color, but unlink it from a Global color so that the object keeps the color even when the Global color is changed? This doesn't seem to be implemented using Designer 1.10.4, which may not be the most current version. I am rarely updating in order to keep workflow stability. I searched for "unlink global color" and didn't find this issue. Best wishes, Shu

Hey everyone! I'd like to be able to name all the selected layers the same. I can do this on iPad, but this doesn't seem to be implemented using Designer 1.10.4 on macOS. This may not be the most current version. I am rarely updating in order to keep workflow stability. I searched for "name multiple" and didn't find this issue. Best wishes, Shu

Hey everyone! Not sure this has anything to do with my system settings being set to German, but I'd like to be able to type "." within the Transform window to do calculations rather than ",", since I'm used to typing "." for floats all the time. This doesn't seem to be implemented using Designer 1.10.4, which may not be the most current version. I am rarely updating in order to keep workflow stability. I searched for ". ," and didn't find this issue. Best wishes, Shu

Hey everyone! Not sure if intended or not, but I can't shift-select some layers within one group, then cmd+click to add another layer within another group, then shift-select within that other group. The last step doesn't work. This doesn't seem to be implemented using Designer 1.10.4, which may not be the most current version. I am rarely updating in order to keep workflow stability. I searched for "select layers different groups" and didn't find this issue. Best wishes, Shu

Hey everyone! It'd be useful if there was an option to move duplicates below the current selection rather than above them. This doesn't seem to be implemented using Designer 1.10.4, which may not be the most current version. I am rarely updating in order to keep workflow stability. I searched for "duplicate below" and didn't find this issue. Best wishes, Shu

Hey everyone! I'd like to be able to set the opacity value of a global color. This doesn't seem to be implemented using Designer 1.10.4, which may not be the most current version. I am rarely updating in order to keep workflow stability. I searched for "global color alpha" and didn't find this issue. Best wishes, Shu

Hey everyone! I'd like to be able to apply a global color to any FX. This doesn't seem to be implemented using Designer 1.10.4, which may not be the most current version. I am rarely updating in order to keep workflow stability. I searched for "global color fx" and didn't find this issue. Best wishes, Shu

Hey everyone! It'd be great to be able to move a gradient without rotating it. Not sure this can be done right now. I guess that would require moving both nodes at the same time. This doesn't seem to be implemented using Designer 1.10.4, which may not be the most current version. I am rarely updating in order to keep workflow stability. I searched for "move gradient rotating" and didn't find this issue. Best wishes, Shu

When you - don't know this limit exists on iPad and you - create a giant palette on iPad's Designer so you - put hours into this and then you - realize there's no IO on iPad and you'd have to - create a palette from scratch for Designer (iPad), Photo (iPad) and both (desktop) so for the sake of saving time you - decide to delete the entire thing, put everything into a .png and use that as a reference instead. That's annoying.

Multiple layer menues for all the layers would be great for moving things frome one place tp another and for copying & pasting.

Does this work on iPad as well?

Hey @Callum Thanks for your reply! I'd say including IO for .psd is already trying to adhere to a standard; being able to handle broadly used file types is there to ensure compatibility. A user expects to be able to go back and forth between softwares that support the same file type and keep their data when doing so. But that isn't the case. I am getting different results. [...(1)] It'd be highly appreciated if this worked as expected. There are many users who use Procreate and Affinity software in combination and .psd is the link between them. Granted, not everyone needs all the layer blend modes, but I'd say it's a matter of professional software to make things work. [ [Can't strike through, so I move it; this is (probably) not the case, since Files.app (probably) just uses the thumbnail cache directly.] (1) In fact, I am getting the same results in Files.app's preview that I am getting in Procreate. So both Procreate's as well as iOS's .psd renderer give the same output for the same values. So unless iOS checks for source, gets "Procreate" and renders accordingly, I guess Affinity is the odd one. ]

Hey @Dan C No worries! It's great news you can reproduce the issue at least at one stage. I'll see if I can upload the files. If so, it can take a while. Uploads are internal access only?

@carl123 Thanks for the sample Macro! I'll have a look! Maybe a generic solution would indeed exceed Macro capabilities, though. Maybe I'll go for a plugin or including it in an app after all. Also, the shape that's located in the middle (or the pink dot in the first example) musn't be altered other than moving the pixels' bounding box to center. So a filter over the entire image will probably not work, I guess.

I can't upload any work files directly. But here's an example file that should include all possible scenarios: Most files are 2048px squared, some may be different, but it's rare. I'd like to remove the blue, green and red dot and only keep the bigger shape in the middle. Maybe I'd have to write a plugin.

Hey @John Rostron! Thanks for your detailed reply! Unfortunately, things are more complicated. Some more things that I maybe should have specified to begin with: - The two dots are on the same layer. - I don't know the colors of the dots. - I only have that one layer within the file. So - No layer jumping needed, which makes things easier, but also - Selection by color doesn't work. - I have to get rid of the pixel data depending on adjacent pixels. I'd have to read where islands are located, look for the biggest island and set the other islands' alpha values to 0. (Maybe there is an easier way to do this, one that might work as a Macro, but I couldn't think of it). Once the stray dot(s) (there may be more of them and I don't know where they are located, or if there are any at all) are gone, the rest should be as simple as including the commands - align to middle horizontally - align to middle vertically. That should work as well and be independend of any actual numerical input from the file, which would be important, because I'd have to run that Macro over thousands of files with different "green dots" and "pink dots".

Hey everyone! Let's say I've got an image like this: and I want to center the pink dot using a Macro. That itself may be very straight forward. But there's also the green dot. I'd have to remove that one first. That could be done manually, but it may be small and transparent enough to not be seen easily. Is there a way to do this using a Macro? I could only think of ways to code this, but you can't write scripts, I guess. _____ EDIT: - The two dots are on the same layer. - I don't know the colors of the dots. - I only have that one layer within the file. _____ Best wishes, Shu

Hey everyone! Not sure this is a Procreate issue or Affinity, but: Using the Add blend mode yields different .psd results in Procreate compared to Affinity. I am getting much brighter areas in Procreate. It's fairly easy to reproduce. Here are the steps: 1. Open Procreate 2. Create new RGB canvas. 3. Select a middle grey color. 4. Create shape outline in Procreate, fill it. 5. Create new layer, clip it to the one below. 6. Set second layer's blend mode to "Add", at 20% opacity. 7. Select a brighter grey color. 8. Paint on second layer. 9. Smudge the brighter grey on the second layer (, clipped Add 20%). 10. Close file. 11. Export to .psd, destination: Files.app. 12. Open Affinity Photo. 13. Open previously exported .psd. 14. The shades on the second layer (20% Add) should show less bright compared to Procreates'). Reimporting the .psd to Procreate keeps the bright colors. The import of 20% to Affinity works. I guess the blend mode calculation is different. I am using Procreate 5.2.6, Photo 1.10.5. I'd expect this happens with Designer and Publisher and on desktop as well (not tested, though). For reference, post on Procreate Folio: https://folio.procreate.art/discussions/4/10/53904 Best wishes, Shu

@Dan C Thanks for the detailed reply and trying to reproduce the issue! That's exactly the setup! With File B containing the same amount of symbol instances and File B once being a duplicate from File A, so the Symbols should have the same name (not displayed on iPad) and might have the same internal id(s), but the content of the Symbols is altered. 1. It didn't crash when opening a file at all. I just noted that step to give more context. 2. This happens when dragging File B into File A, while having File A open, so that File B is embedded into File A. 3. That happens when closing File A after having embedded File B into it. I thought about going desktop, but it was still faster not having to go back and forth, since I do need those files on iPad eventually. What made me think of device limits as well: The faster I worked, the more likely for the crashes to occurr. When I tried working very slowly, no crashes happened. Of course, hardly any work happened then as well. Might be that for - crash by drag & drop B into A to embed: The new layer's pixel data may not have been pushed to the GPU and it's already used. - crash by closing File A: The file may not have been written completely and you're already trying to access it. Note that sometimes, the thumbnail will not be showing an updated version after closing the document, even without a crash occurring, until I open and close the file another time. Also note that this already happens with only a few files in the document browser, so I guess it's not a RAM issue. Also, the files are very small and don't contain any pixel data until rasterizing File B into File A, which is only the second step in the overall procedure where no crashes happen anymore. [Besides that, a completely independant issue, since it also happened without embedding files - but still similar in nature: I also noticed crashes when drag & dropping too many files at once from Files.app to Designer's document browser. Had a few hundred files there and dropping a batch of 9 files regularly resulted in crashes, while dropping 5 files, then 4, always worked. But that, as well, shouldn't have hit the 3GB. Note that when that issue occurs, the files' previews reorder rather slowly after having dropped new files there and it also requires maybe 50 to 100 files already located in the document browser.]

Hey everyone! Yesterday, I ran into about 100 crashes. I had to embed a few hundred files into another few hundred files and rasterise the embedded files. I made this a two steps process of - embedding all files - rasterizing all files The crashes happened when - Opening a file - Drag & drop another file from Files.app overlay (Potential crash! When reopening Designer, the other file was already embedded.) - Closing the file (Potential crash! When reopening Designer, the other file was still embedded.) Each crash suspended Designer. Each time when reopening, I had to sit through the splash screen loading procedure. I didn't screen record this, since it would have contained the artworks. But I can say there were quite a number (maybe a few hundred) of symbol instances both within the files that are supposed to contain the embedded ones as well as within the files that are supposed to be embedded. So you may be able to reproduce this by spamming a few groups of symbol instances across a file, duplicate it and try to embed it into the original. I tried using Photo to do this, but the same issue shows up there as well. I am using iPad mini 5 and iOS 15.4.1. I searched for "crash embed file", 3 results, not about this. Best wishes, Shu

Running Macros while not being able to add new ones is indeed quite limited!

Running Macros while not being able to add new ones is indeed quite limited! EDIT: For reference:

@NathanC Alright, thanks for the reply! Wasn't obvious to me that specifically having a selection within a group would retain that group's expanded state as well as the selection within, while outside selections and groups' expanded state without child selections would not be retained at all. Quite specific. But I guess it can be useful that way, when you know the behaviour.