https://bugs.kde.org/show_bug.cgi?id=408369
--- Comment #2 from Vanessa <enygmano...@gmail.com> --- Dear Ahab GreyBeard Thank you for your very prompt response to my report on the issue, and also your candid advice for the solution. I do apologize for my information being vague, I am sadly inexperienced At this sort of thing and I hopefully will get better at it soon, And I also do apologize for the Double bug report, I thought the problem was So I add it to the first, and again I apologize for my lack of experience I was about ready to say the recent update fixed the problem and tell you it is not an issue anymore but I just ran into the problem again, But your advice saved me some headache And it's working like it should. I honestly didn't know that, I was able to do it before...To be honest with the recent updates I am trying my best to relearn some of the mechanics...^^; and learn to properly use this amazing art program, I honestly gotten in full swing with Krita around October of last year, I am sorry for my rambling. And I actually don't need to go over the vector layer copy bug, I am running the program now and I reproduced the problem I had problems with earlier, and the new update took care of it, now I can duplicate the Vectors easily now, without worrying about it being destroyed. Which is what I was facing with before the update, and I don't have to chase it around on the original, when it should have been on the layer copied... I hope that explains the problems and Thank you For taking care of the problem it has been very helpful. And you just save me from alot of hard work in the long run. Take care and Have a nice day. Also Thank you for your time. On Thu, Jun 6, 2019 at 1:00 AM Ahab Greybeard <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=408369 > > Ahab Greybeard <ahab.greybe...@hotmail.co.uk> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |CONFIRMED > Ever confirmed|0 |1 > CC| > |ahab.greybe...@hotmail.co.u > | |k > > --- Comment #1 from Ahab Greybeard <ahab.greybe...@hotmail.co.uk> --- > I've set this to Confirmed because there is at least one problem with > selections. > > I've tested this with the recent 4.2.1 Linux appimage release: > > If you start a selection sequence with the Selection tool set to Subtract, > it > will effectively subtract the selected shape from the entire image > selection. > After that, it does look as if the Subtract option adds to the shape but > it is > in fact subtracting from the selected area which is the region outside the > first shape. (Does that explain what is happening?) > > If you then use Intersect, there is a strange effect where there are two > nested > dotted regions. > > If you use the Replace or Add option as your first selection in a sequence, > then the process has a 'look' that is more normal. However, the Intersect > action then has a malformed outline. > > I think that it shouldn't be possible to use a Subtract as the first > selection > operation on an image that has no active selection. This is a matter for > higher > level discussion somewhere. > > As for copying vector layers, there is an existing bug about Duplicating > vector > layers: https://bugs.kde.org/show_bug.cgi?id=408028 but you'd need to > provide > more information about why you feel it isn't working like it used to. Also, > that vector layer problem should be as a separate bug report if you want > to go > into more detail. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
