@Boldline Should have been fixed (tested here). I will reopen this bug.

@Boldline Seems to be sensitive to zoom level. I added this to the backlog as a bug. It works here at around 300% zoom level.

@pentool Dragging the toolbox from the side to resize is not possible in VS.

@VectorStyler Could the EditingOptions-2 setting "Show Nodes when Hovering" also be made applicable to the Shape Editor mode? What I want to achieve with this is the opposite. The ability to disable Show Nodes in this mode when hovering. Show nodes/handles when I click/select a shape similar to how it is now. Actually a kind of intermediate step.

@b77 nice, thanks. I didn't think about the Appearance panel for the opacity. The opacity feature of the Gradient panel adjust the opacity of one knob & it seems that it is the first (left) one by default. It works well through the appearance panel except that I can't use the cursor... I have to enter a value (a bug I suppose). I've just noticed that we can combine opacity values from the Gradient and Appearance panels, quite tricky afterwards to remember if one or both were changed.

@Pat I could not replicate this at the first try, will try more. @b77 This is in the Noise Browser view, in the Noise image effect (or any other effect using the noise), Noise drop down -> Browse Styles.

@Boldline I could not replicate this. Send me that example by email.

@Boldline Got the file. The error can be replicated here also.

@Boldline said in Scaling live text still causes font size discrepancies: @VectorStyler do you need me to send you the font file? would that be a factor? It could be, but no need to send it for now.

@VectorStyler if you need anything from me, let me know

@VectorStyler no problem. To clarify, I was just meaning it's not a "new build issue", it's been there for as long as I can remember. Why it never got brought up on the forum, who knows! It's not keeping me from doing work, so it's not a rush issue personally.

@VectorStyler I sent you the file

I upgraded to Build 91 and also deleted my workspace and settings files and restarted VS. I recreated the same setup as before where I made two spot color rectangles of different colors on two different VS documents and clicked between the two files. There are still issues as related to the custom palette but the appearance panel and color panel work properly. It's only registering the color in the custom spot color palette during the shape's initial creation. When I click over to the other file and click back and reselect that shape, nothing registers still in the custom spot color palette. Here is the video showing this in the new build 91 I also removed the custom palette completely and set the new file back to essentially to default settings and the default palette highlights the appropriate color each time, whether I click off or switch files in between. I ran one more test - I replaced the custom spot color palette file (ase) with a different custom spot color palette (ase) and everything worked properly as it should. So the issue seems to be with that specific "ase" file, the custom spot color file. @VectorStyler I sent you that troublesome ase file as well as the custom ase file that does work properly in build 91 to help deduce the issue between them

@VectorStyler I don't know anything about the app programming logic, but maybe we can check each member of the group? If it is an object without strokes, we can prevent it from getting affected by the Expand Stroke command. Unless it is very heavy to loop through all members of a group like that, since a group could consist of thousands of members

@Boldline Added this to the backlog.

@VectorStyler said in Pasting vectors from other projects causes main palette issue: Were these added manually? or just appeared after opening on the desktop? those must have been added by VS because I did not add them myself. I will email you the file now

@Boldline I will try to find out what could cause this.

@VectorStyler Sorry for the delay - sending now

@VectorStyler I tried again after another restart of VS and it's working again... I don't know. I tried to do the due diligence before reporting it. It was persistent even after restarting before. I'll let you know if it happens again