https://bugs.kde.org/show_bug.cgi?id=388307
--- Comment #4 from kdex <k...@kdex.de> --- (In reply to simeirxh from comment #3) > (In reply to kdex from comment #0) > > 1) Press `Q` to select the multibrush tool in an image. > > 2) Not sure if this setup is really necessary, but I set the tool up as > > follows in the "Tool Options" tab: > > > > [Basic Smoothing] > > [ ] Assistant > > [x] Snap single > > [x] Show Axes > > Axes Angle: 0.0° > > [Mirror] > > [x] Horizontally [ ] Vertically > > > > Make sure to verify that it works as expected by drawing: i.e., if you draw > > something on (x, y), the same value should appear on (-x, y) if you imagine > > the horizontal center lies at x = 0. > > > > 3) Now, scale the image up. In my case, I resized an image from 64×32 px to > > 1024×512 px, hence keeping its proportions. > > > > 4) Try to use the multibrush tool again. If you show the axes (in the tool > > settings), you will see that they still apply to the old image of dimensions > > 64×32 px. Essentially, this breaks the multibrush tool and requires the user > > to save, close and re-open the image for the axis to be recalculated. > > > > I would have expected these axes to be recomputed whenever the image size > > changes. > > Hi, > > I looked into this issue. You can actually reset the axes by clicking the > "Reset" button under the "Show Origin" checkbox in the tools options docker. > I would say how it works now is better than automatically change the > positions of the axis immediately after changing the size of the canvas, as > sometimes artists might want to have the axis remain where it is. Maybe we > should add this to the wiki? I don't have that button/checkbox in my docker (krita 3.3.3). Anyway, I can't see the usefulness of omitting the axis reset after the resize. What useful properties would this yield? Depending on how you resize the image, it's likely that the new axes don't even touch the image anymore. IMHO this would lead to questionable UX and to artists getting confused, including myself before I figured out why the multibrush tool had stopped working (which in turn is why this ticket exists in the first place). ;) -- You are receiving this mail because: You are watching all bug changes.
