@Gremriel This problem was replicated (finally), and the fix should be in build 1.1.048

@encart that's what I like about experimenting and associating you try out a diffuse idea it evolves and you find something spectacular

@Igull This sounds like a bug. I added it to the backlog.

@plrang Maybe it happens only with complex drawings?

@VectorStyler Thanks for explaining - makes sense now. A solution has been elusive so far but I have total faith you'll eventually find a great solution. Until then we'll make do!

@Boldline For more complex shapes where the blending is not exactly right due to node count differences sometimes adding a node or two is needed.

@VectorStyler said in Taking a preferences file used on an intel mac and installing it on an M1 makes the artboard all gray: @Boldline Check the display mode in Preferences -> Performance. OpenGL is not working on M1. Yes that was the issue. When i switched the display mode to metal, it worked just fine in the M1 - thanks! (this preferences file did not fix the issue with making cusp nodes with the pen tool - so that must be something else)

@VectorStyler some interesting observations when I tried out settings on the pattern brush. I had forgotten to use "convert to curves" in order set the shape to a path. So it appears, when the shape is used instead of a path, it creates that unwanted gap. However, I can use the shape, set it to "rigid shapes" and then if I hit the "scale rigid shapes" it will give me the perfect gap-free pattern in an oval. [image: 1657642958079-e2625a6d-1233-4a61-b302-feab0a181048-bld-2022-07-12-at-12.22.22.png] 0_1657643122202_pattern brush gap.vstyler

@encart This is a bug, will be fixed ASAP.

@VectorStyler Here it is after a factory reset so that my preferences do not affect behavior.

@Boldline I will try to replicate this issue. Added it to the backlog, let me know if you have more info.

@Boldline @b77 This can be replicated, and it seems to be a precision bug in the divide operation. It can be worked around by adjusting the handles.

@Boldline This seems to be a regression, as hairline width strokes should not be expanded. As a workaround turn off stroke expansion for Divide: in the Path panel menu -> Shape Combine Options, select Divide for the Operation and uncheck Expand All. I added this to the backlog as a bug.

@Boldline said in Cursor Icon Changes: @Igull Interesting - how would you know it was selected? How would you go about selecting something behind it? Normally, to select an object that's below another object, you just click some visible part of the other object or you can command click to drill down to it. As soon as you mouseover an object in any other app, the object highlights - either by changing the outline colour or (as in VS) it will highlight it's nodes and outlines some way. That shouldn't change when you mousedown over the object, the nodes etc are still highlighted, you are just not transforming them - only offering the ability to move the object. You should only be able to transform the object by selecting (ie click and release the mousebutton - mouseup) it with the transform tool then use the same tool to do the transform or simply use the shape editor directly - without the need to select. Having said all that, if that is no longer the way you want it to work, then a preference would be the solution to allow that option for geriatric folks with all those years of muscle memory and ingrained understandings of the way things are (were ). Neil

@b77 said in Conflicting Keyboard Shortcuts: Not sure, but maybe doing the same with the 'C' key for the Collider tool would be useful? Will do that.

@Boldline said in Issues always occur if mistakenly set to Transform option (select and transform members of grouped objects): @Ok thanks that helps. Can we delve further in the second issue in that post? If I mistakenly use the wrong transform tool version and it creates a mess like in the screenshot. If you go back in the history panel you can't recover it In the file I have I could not find the "Expand Clipped Objects" step. BTW: if the "Expand Clipped Objects" is used on objects inside a clipped group, but not on the whole group, then there might be some issue.

@fde101 Yes, the "Actual Size" zoom mode will result in a discrepancy.

@b77 Yes, I accidentially assigned C to the corner palette first, where it worked flawlessly, but thanks for the suggestion!

@Jayanta-Das said in Some bugs with Coner points and centre pivot: This is what other program does. And I think this is more easy to manipulate. I added this to the backlog, will try to find a solution.

@VectorStyler Yes Opacity would be more appropriate.