shushustorm
-
Posts
367 -
Joined
-
Last visited
Posts posted by shushustorm
-
-
Yes, I did mean "only" having to expand and collapse one apple, but it's some unnecessary boxing that you always have to fight through and that adds up quickly when you're working with a few hundred, and dozens of different, symbol instances that all are buried within different parts of the layer hierarchy. I just tried disabling the syncing process for disabling a symbol and it works flawlessly! That's great and possibly a nice solution for many scenarios!
-
Thanks for the reply!
Well yes, if it's still an issue with the current version of Designer, it should be fixed. If not, that's great!
I'm not sure I'd say this is due to no transparency support for global colors. In fact, I'd say if transparency was ignored completely, this issue shouldn't show up at all. So in fact, I guess up to some point, they do work with RGBA rather than RGB and the preview gets issues, since there's no full support for it. Seems like the color is just added to an rgba(0,0,0,255), so, for example, for a 20% green, you have:
rgba(0,255,0,51), but that's not just solidified to
rgba(0,255,0,255). Instead, it seems those are blended:
rgba(0,255,0,51) and rgba(0,0,0,255).Also, maybe I should have described the issue a little more precise.
1. I have a shape and its fill is set to any color, with the color's opacity set below 1, for example, 20%.
2. I add a document palette.
3. With the shape selected, from the Swatches menu, I select "Add current colour to palette as a global colour."
4. The global color appears in the Swatches menu listed as the document's global color, but its shade is darker than what it's supposed to be. -
It's a very sporadic issue. Only ever showed up once. So I tried to get more info here whether there is a known scenario so I can avoid it.
Also, the app used up more and more memory without changing anything within the file. Just by focusing and defocusing some times, the RAM usage went from a few hundred MB to above 1GB.
I'm not unwilling to update in general. But there's a time for it that makes sense and then there's a time for it when things run quite well and I don't need any features of newer versions - why would I risk breaking things by updating? That doesn't mean I don't appreciate bugs fixed in future versions down the road when I'm updating.
-
Let's say I have a tree with apples:
Tree
-> Apple (Group)
---> Apple (Symbol)
-> Apple (Group)
---> Apple (Symbol)
-> Apple (Group)
---> Apple (Symbol)
-> Apple (Group)
---> Apple (Symbol)
Now I want to disable some of the apples to focus more on the individual design. So I disable some groups. Now I want to change the Apples' shapes. So I need to expand Apple (Group), then Apple (Symbol) instead of just Apple (Symbol). And the same when collapsing later on. It just creates one unnecessary layer of abstraction that you always have to work through.
-
I wanted to make a short version of this my signature, but I haven't found a way to set one, so I'll just post here:
Since it's often topic of debate: I update rarely to ensure workflow stability. Even after point releases I am sometimes facing severe issues, which result in countless hours of additional work. When I'm in a place that only shows less severe issues (that I still consider worth reporting), I typically stay there for quite a while. Not to mention files sometimes not being backwards compatible after having worked on them for some hours or days in a new version, just to discover a severe issue, which may or may not be fixed in maybe a few months' time. So you're trapped with that version including the issues. If _potentually_ "outdated bugs" are not wanted here, a moderator or Serif employee shall message me and I will no further report any bugs. No hard feelings.
Touche! But really, I am just reporting some hiccups. Have faced much more troublesome issues. Quality issues. Data loss. File corruption. ....
-
Hey @Callum
Thanks for your reply! Since I scaled down the lower green square shape (in the layers panel, it's the upper symbol) to 50%, I'd also expect the star to be scaled to 50% when making it a child of the scaled down green square.
It seems to work sometimes, but I haven't figured out if both options (scale by symbol parent / keep own scale) are features I don't know how to access specifically or if one is intended and the other one is a sporadic bug.
-
Awesome! Thanks for forwarding!
-
Thanks for the reply, @walt.farrell!
I mean unchecking the check so the Symbol isn't visible anymore.
Interesting idea about stopping syncing! That may very well work in some scenarios! Hiding a group is generally more straight forward, but:
- it creates unnecessary overhead, especially when using the symbol a lot and
- you always have to expand and collapse the group(s), which is continuous workload!
-
Thanks for clarifying. That's what I did eventually, but I'd like to avoid typing the % all the time. But that doesn't work, unfortunately, since it auto completes to a number I didn't type.
I though so. I don't think that's a good idea, however, since it makes things quite obscure. You have to think what to type instead of just typing what you need. So I'll probably be just better off typing all the way to the % symbol and still be faster. Unfortunately. Not to mention I can't type single digits. So I'd have to keep in mind even different behaviours for just one field.
Want 10%? Type 1
Want 5%? Type 5%
Madness!And that behaviour is not aiming for consistency either. I don't have to type "100px" to get "100px". I just type "100" in a field that uses pixels and it auto completes the metrics. But never messes with the values. Unless when typing percentages.
-
Ran into this the other way around:
This time, the bounding box of some layers exceeded the file resolution, which resulted in the slices' bounds being placed outside of file bounds. Haven't yet found a better solution than just scaling down each one individually.
-
Awesome! Thanks for your replies!
I'm on a Mac like Bruce, so I'm going to have a look, seems like those settings may be able to change Affinity's behaviour as well! But, granted, an option within Affinity would be great in order to not require overwriting of system settings.
-
Awesome! Thanks for pointing out!
-
It'd be great if there was an option for RGBA global color rather than just RGB. I guess you should be able to choose. I'm not using noise myself, but being able to make noise sync for consistency makes sense as well.
For reference:
-
Thanks for the reply! Haven't tried that! I'll see if that works!
EDIT:
I just tried that, and while it's not the ctrl key, it does work by holding the cmd key (I'm on a Mac).
-
Interesting. I'll have to have another look; didn't think I ran into this using other sliders, but may very well be the case.
-
-
Hey everyone!
Here is a video showing the issue:
https://www.shushustorm.com/_Uploads/Serif/macOS/1_10_4/ShapeDoesntScaleToSymbol.movI 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 "scale symbol" and didn't find this issue.
Best wishes,
Shu -
Hey everyone!
Here is a video showing the issue:
https://www.shushustorm.com/_Uploads/Serif/macOS/1_10_4/SymbolDoesntSync.movI 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 "symbol sync" and didn't find this issue.
Best wishes,
Shu -
Hey everyone!
- I am trying to align multiple selected shapes.
- I have transform multiple shapes enabled.
- I click on center horizontally.
- I click on center vertically.
This doesn't result in the shapes being centered to the document. It seems to center the shapes to their average shape center. The setting for transforming multiple elements doesn't seem to have any effect here.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 "align multiple" and didn't find this issue.
Best wishes,
Shu -
Hey everyone!
Not sure this is intended or not, but it would be great if one was able to disable select instances of a symbol and not all at once. I am trying to disable the instances, not its contents. Right now, I have to encapsule each instance within a group to be able to disable it.
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 "disable symbol" and didn't find this issue.
Best wishes,
Shu -
Hey everyone!
I ran into Designer showing the beach ball whenever I moved full screen focus to it. Looking into the activity monitor, it showed more and more increasing RAM usage by Designer. The file was getting somewhat complex, so I closed it and opened a very small file. The issue still showed up. Had to restart Designer and the complex file now works fast again. Not sure what caused it. Working on that same file, this didn't show up later anymore. Seems sporadic.
Is there a known issue with Designer 1.10.4 getting memory leaks? This may not be the most current version. I am rarely updating in order to keep workflow stability.
I searched for "memory leak" and didn't find this issue.
Best wishes,
Shu
-
Hey everyone!
Having a document palette and a shape that uses a color that's supposed to be transferred to a global color, the color's preview will be darker by the amount of 1.0-opacity.
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 "global color preview" and didn't find this issue.
Best wishes,
Shu -
Hey everyone!
When typing the opacity value of a color within the color picker, then Enter, the typing cursor will still be there. Trying to stop typing by Escape quits full screen instead.
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 "exit typing escape" and didn't find this issue.
Best wishes,
Shu -
Hey everyone!
When I have an object and I toggle another bounding box, it gets reset to its previous one when
- duplicating an object or
- rotating it 90 degrees or -90 degrees
- mirroring it on X or Y
This can be quite annoying when you need to use that bounding box, especially when the original box doesn't retain the shape, but is rotated for whatever reason (may be a bug itself).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 "selection box" and didn't find this issue.
Best wishes,
Shu
Align multiple shapes not working
in V1 Bugs found on macOS
Posted
Thanks for your replies,
@Callum
@v_kyr
Alright, when I align from the toolbar, I can change the settings to "Spread" for both horizontal and vertical alignment and I do get the results that I want (both shapes being centered to the file's center).
However, I would expect that, when directly aligning from the context toolbar, while having "Transform Object Separately" (also context toolbar) enabled, the objects are transformed separately, so they should be aligned separately, which again, should center them to the file's center, since that's what happens when I select them individually and try to center them horizontally and vertically.