Schubi63

Hi folks,
 
I couldn't find an option to expand / collapse all child-groups/child-layers when pressing the little arrow button in front of a group/layer that contains child objects.
 
I know this function from Phxxxxxop, and used it a lot to rapidly collapse all expanded child-elements and quickly get an better overview of the layer hierarchy.
 
Phxxxxxop provides that functionality by pressing alt+click. And if you have used it - the next alt-click causes the opposite (e.g. expand all).
 
I liked and used it quite often.
 
 
Cheers guy,
Stefan.

Hi folks,
 
I couldn't find an option to expand / collapse all child-groups/child-layers when pressing the little arrow button in front of a group/layer that contains child objects.
 
I know this function from Phxxxxxop, and used it a lot to rapidly collapse all expanded child-elements and quickly get an better overview of the layer hierarchy.
 
Phxxxxxop provides that functionality by pressing alt+click. And if you have used it - the next alt-click causes the opposite (e.g. expand all).
 
I liked and used it quite often.
 
 
Cheers guy,
Stefan.

If you right-click and choose "Expand Selection" or "Collapse Selection" it will apply to all child objects.
 
Not the best solution, but it's there. Holding a modifier key (option) like in Finder's list view would be better.

Hi folks,
 
I couldn't find an option to expand / collapse all child-groups/child-layers when pressing the little arrow button in front of a group/layer that contains child objects.
 
I know this function from Phxxxxxop, and used it a lot to rapidly collapse all expanded child-elements and quickly get an better overview of the layer hierarchy.
 
Phxxxxxop provides that functionality by pressing alt+click. And if you have used it - the next alt-click causes the opposite (e.g. expand all).
 
I liked and used it quite often.
 
 
Cheers guy,
Stefan.

Hi folks,
 
I couldn't find an option to expand / collapse all child-groups/child-layers when pressing the little arrow button in front of a group/layer that contains child objects.
 
I know this function from Phxxxxxop, and used it a lot to rapidly collapse all expanded child-elements and quickly get an better overview of the layer hierarchy.
 
Phxxxxxop provides that functionality by pressing alt+click. And if you have used it - the next alt-click causes the opposite (e.g. expand all).
 
I liked and used it quite often.
 
 
Cheers guy,
Stefan.

Hi folks,
 
I couldn't find an option to expand / collapse all child-groups/child-layers when pressing the little arrow button in front of a group/layer that contains child objects.
 
I know this function from Phxxxxxop, and used it a lot to rapidly collapse all expanded child-elements and quickly get an better overview of the layer hierarchy.
 
Phxxxxxop provides that functionality by pressing alt+click. And if you have used it - the next alt-click causes the opposite (e.g. expand all).
 
I liked and used it quite often.
 
 
Cheers guy,
Stefan.

yes, please.  :)

...or Command+J, as usually in the Draw Persona.
 
 
Wow, I completely overlooked the "Export preset" part. Didn't know why, but I thought it was some image format configuration :wacko: This helps a lot!
 
Thank you all for the comments!

Hi Lojza,
 
that's true. But if you want to duplicate the export settings of a slice you have at least the possibility to copy the settings from one slice to another. Unfortunately therefore are no customizable short cuts provided.
 
 
Best, Stefan.  

+1

Hi al,
 
it just happened that I had to changed my document size by adding pixels to the LEFT side of the canvas. What I realized later, was that all slices went to the "wrong position" caused by the canvas modification.
 
At least a warning / hint / dialog would have been nice at the point of altering the document size.
 
A file dialog that in case of having slices (which are constrained to canvas size) that offers to:
1) just ignore slice positions and
2) calculate the new positions + alter them automatically
 
would be very nice here ;)
 
 
 
Thanks for thinking about it,
Stefan. 

Ha! Good old auto-correct... *sigh*

The plan is that Affinity Photo will be kept 'in sync' with a simultaneous Photo 1.4.4 that can read Affinity Designer 1.5 files. Then when Affinity Photo 1.5 is ready to release there will probably be an equivalent simultaneous Designer 1.5.1 release to keep everything in sync again regarding supported features and files.
 
 
Bear with us, we are tweaking one or two things behind the scenes... When it's ready it will prompt.
 

Status: Release Candidate
Purpose: New features, fixes
Requirements: Purchased Affinity Designer
Mac App Store: Submitted
Download: 1.5 RC1 Here (Updated at 15:31 BST to include a few extra bits)
 
This is a beta of a substantial change to our codebase and as much as we have tried to ensure the quality of the code, it should be considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that you may be adversely affected by the application failing. In addition it is definitely worth noting that files created in Affinity 1.5 cannot be opened in 1.4 so always make a copy of your important documents before opening them in 1.5 to ensure you do not accidentally overwrite them and are unable to open them in your 1.4 version.
 
To use this beta, simply download the file from the link given above and double-click on the file to open the installer. Follow the instructions to install the beta version. The beta sits alongside the Mac App Store version and will not interfere with it.
 
Fixes/Improvements:
macOS Sierra improvements (some dialogs were not getting their input boxes auto-selected which was a nuisance) Sharpen Tool (in Pixel Persona) now correctly performs Blur when holding down Alt/Option Auto-selecting layers with the new Preferences item won't force expansion of selected group nodes now Updated Assets Fix for colour conversion issue seen when copy/pasting a placed image which is of a different colour profile to the document Layer effects now allow the user to type in values in different units (points, inches, etc) Huge performance increase for marquee selection of objects in multi-artboard documents Correctly import miter limit in SVG documents PDF import and export of transparency groups should be much improved now Aligning objects in a symbol instance failed to redraw the newly aligned objects in other symbol instances Better logic for dragging out an Asset with constraints on it while Cmd is held PSD export of raster clipping masks improved PSD import fixes and improvements relating to solid white layers and being able to optimise and just use an opaque white document instead Slice Tool should respond to Escape correctly now Fix for occasional Symbol issue manifesting as the detachment of all attributes when only one is changed EPS and PDF import now generate documents with better structure when a large number of children nodes are imported Draw 'thin' lines in a visually nicer way Fix for crash when creating a Compound from a constrained object Fix for releasing compounds causing objects to move around if the contained objects had constraints Fix for solid fills not applying to pixel layers Pasted text should work correctly with text styles now Temporarily removed 32bit document format and functionality as this has not received enough testing coverage to release Fix for constrained objects in symbols acting strangely Miscellaneous other small fixes

Hey Schubi63,
 
On the Windows version, it is the other way around so I think this is a bug or at least an improvement for the Mac version. I'll get this logged for you.

Thanks! :)

Alternatively just select the top node which u want to keep; then nudge it over using the arrow keys a set amount (2 clicks is usually enough). Then select and delete the lower node. Select the upper node u nudged, and nudge it back the same number of clicks as before but in the opposite direction.

I am using the Windows beta.
 
Try this. Select both nodes by dragging the selection marquee around them with the node tool. Now hold the shift key and select the top node. Press delete. that should delete just the bottom node.

Hey guys,
 
I don't know if I'm totally wrong, but see slightly advantages of having ellipsis per default in the middle of names. Especially on filenames.
 
Maybe that's why Apple uses ellipsis in its Finder also in the middle of the filenames. I'm sure you can change it - but I haven't had any reason to do so since years.
 
I would say it is more likely to have names like:
 
"wizardMockup_01"
"wizardMockup_02"
"wizardMockup_03"
  or   Affinity Designer Beta 1.5.9 Affinity Designer Beta 1.5.10 Affinity Designer Beta 1.5.11   So that names can be read much better if the ellipsis is not in the and, like it is in AD (in AP I guess too)
 
 
If you don't think it would make sense of all users - put it into the preferences. :)

Hello,
 
I would like to have this "nice-to-have" feature: an ellipsis for names (of objects, layers, groups) in layers window.
 
If you put it on your list, see also: 
https://forum.affinity.serif.com/index.php?/topic/24596-ellipsis-per-default-in-the-middle/
 
:)
 
 
Thanks for your work and passion to create that piece of software at all,
Stefan.

I agree with this request. A user can have a full palette of custom swatches, but the user can't find those colors (easily) without a palette in the Effects panel.

Hi,
 
it would save a lot of time if the layer fx "gradient overlay" AND outline ("Umrandung" - see 3rd attached image) would have the same functionality as "color overlay": the ability of choosing swatches - gradients in this case.
 
For a vice versa functionality - see also:
https://forum.affinity.serif.com/index.php?/topic/25422-how-to-get-a-color-gradient-from-layer-fx-into-swatchesgradients/
 
 
Thanks for taking your time and thinking about it,
Stefan.

I understand now! My thanks to both of you.

Exactly.
 
I created a gradient in a layer fx (gradient overlay). That gradient I want to "extract / re-use as a fill in other objects which have their own (different) layer fx. So a swatch would be the solution here. 

Hi Alfred,
Not necessarily, because that will copy all the FX effects to the style/object (the gradient was created as a Gradient Overlay effect in the Layer Effects panel, not as a regular Fill). If I understood correctly Stefan wants to save the gradient as a colour swatch from that panel. Copying the FX also has the disadvantage of forcing the rasterisation of the layer the effect will be pasted on.

This is fixed in the latest beta now, will be release sometime this week I think. :)
 
I'm moving this to the beta forum since this is a beta feature.