Summary: | Hi, when I try to manipulate a gradient fill on a vector layer, every time I move a stop other than the left one, the program will ignore it and move the left one, making it impossible to work with gradients. | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | AxBlack <a.x.sketch1999> |
Component: | Layers/Vector | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | a.x.sketch1999, ghevan, ginoba, halla, shzam |
Priority: | NOR | Keywords: | triaged |
Version: | 5.0.2 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
system info
bug video vector gradient editor issue 4.4.7 |
Description
AxBlack
2022-01-27 03:57:24 UTC
Works fine here. Can you please paste the output of Help -> Show system information for bug reports? (In reply to sh_zam from comment #1) > Works fine here. Can you please paste the output of Help -> Show system > information for bug reports? Hi, thanks for replying, I'm trying to send the information, but it won't let me upload it because it marks it as spam. (In reply to AxBlack from comment #2) > (In reply to sh_zam from comment #1) > > Works fine here. Can you please paste the output of Help -> Show system > > information for bug reports? > > Hi, thanks for replying, I'm trying to send the information, but it won't > let me upload it because it marks it as spam. I'm not sure, have you tried uploading it as an attachment? Created attachment 145995 [details]
system info
Created attachment 145996 [details]
bug video
(In reply to sh_zam from comment #3) > (In reply to AxBlack from comment #2) > > (In reply to sh_zam from comment #1) > > > Works fine here. Can you please paste the output of Help -> Show system > > > information for bug reports? > > > > Hi, thanks for replying, I'm trying to send the information, but it won't > > let me upload it because it marks it as spam. > > I'm not sure, have you tried uploading it as an attachment? I already could, I sent it as "submit patches", I included a video of the bug. I still can't reproduce it, neither on Linux nor on Android :( I wonder if this is a windows bug, deif_lou I remember you talking about something related, do you have any idea? (In reply to sh_zam from comment #7) > I still can't reproduce it, neither on Linux nor on Android :( > > I wonder if this is a windows bug, deif_lou I remember you talking about > something related, do you have any idea? No, I really have no idea, but I would say that it is more related to the new vector system of Krita 5, because I don't have that problem with the one in Krita 4. Created attachment 146002 [details]
vector gradient editor issue 4.4.7
I remember seein that behavior. But I cannot longer reproduce it on linux.
I think the underlying issue is not with the new gradient editors, bur with some weird bouncing back of signals. Something like if the gradient editor emits a gradient changed signal and then that provokes somewhere another gradient changed signal that is caught by the gradient editor and makes it reset (or something like that).
But I think that odd behavior was already present on earlier versions, as shown in the attachment. I don't know if that's what was fixed. I remember taking a look at the code at that time, but found it too convoluted.
(In reply to Deif Lou from comment #9) > Created attachment 146002 [details] > vector gradient editor issue 4.4.7 > > I remember seein that behavior. But I cannot longer reproduce it on linux. > > I think the underlying issue is not with the new gradient editors, bur with > some weird bouncing back of signals. Something like if the gradient editor > emits a gradient changed signal and then that provokes somewhere another > gradient changed signal that is caught by the gradient editor and makes it > reset (or something like that). > > But I think that odd behavior was already present on earlier versions, as > shown in the attachment. I don't know if that's what was fixed. I remember > taking a look at the code at that time, but found it too convoluted. I see, it's a shame. Thank you very much anyway. Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. (In reply to Bug Janitor Service from comment #11) > Thanks for your comment! > > Automatically switching the status of this bug to REPORTED so that the KDE > team > knows that the bug is ready to get confirmed. > > In the future you may also do this yourself when providing needed > information. Thank you very much😁. (In reply to Deif Lou from comment #9) > But I think that odd behavior was already present on earlier versions, as > shown in the attachment. I don't know if that's what was fixed. I remember > taking a look at the code at that time, but found it too convoluted. I remember fixing pretty much the same issue in commit: 627782be4400e61a590440b44a5f33a00c1fd1d7 (refs/pullreqs/975). Also I can't reproduce this on my windows system ... :( (In reply to sh_zam from comment #13) > (In reply to Deif Lou from comment #9) > > But I think that odd behavior was already present on earlier versions, as > > shown in the attachment. I don't know if that's what was fixed. I remember > > taking a look at the code at that time, but found it too convoluted. > I remember fixing pretty much the same issue in commit: > 627782be4400e61a590440b44a5f33a00c1fd1d7 (refs/pullreqs/975). Also I can't > reproduce this on my windows system ... :( So, is it a problem that only happens to me? :'( I tried this on master (08828d1d7b) macos and could not reproduce the issue. *** This bug has been marked as a duplicate of bug 449122 *** |