Bug 449223 - 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.
Summary: Hi, when I try to manipulate a gradient fill on a vector layer, every time I ...
Status: RESOLVED DUPLICATE of bug 449122
Alias: None
Product: krita
Classification: Applications
Component: Layers/Vector (show other bugs)
Version: 5.0.2
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2022-01-27 03:57 UTC by AxBlack
Modified: 2022-02-14 12:21 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
system info (1.40 MB, text/plain)
2022-01-27 17:14 UTC, AxBlack 		Details
bug video (1.38 MB, video/mp4)
2022-01-27 17:14 UTC, AxBlack 		Details
vector gradient editor issue 4.4.7 (84.04 KB, image/gif)
2022-01-27 22:02 UTC, Deif Lou 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description AxBlack 2022-01-27 03:57:24 UTC 
SUMMARY
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.
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 sh_zam 2022-01-27 08:31:41 UTC 
Works fine here. Can you please paste the output of Help -> Show system information for bug reports?
Comment 2 AxBlack 2022-01-27 16:41:12 UTC 
(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.
Comment 3 sh_zam 2022-01-27 17:01:05 UTC 
(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?
Comment 4 AxBlack 2022-01-27 17:14:05 UTC 
Created attachment 145995 [details]
system info
Comment 5 AxBlack 2022-01-27 17:14:29 UTC 
Created attachment 145996 [details]
bug video
Comment 6 AxBlack 2022-01-27 17:17:18 UTC 
(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.
Comment 7 sh_zam 2022-01-27 19:56:26 UTC 
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?
Comment 8 AxBlack 2022-01-27 20:32:03 UTC 
(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.
Comment 9 Deif Lou 2022-01-27 22:02:30 UTC 
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.
Comment 10 AxBlack 2022-01-27 22:38:10 UTC 
(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.
Comment 11 Bug Janitor Service 2022-01-28 04:37:48 UTC 
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.
Comment 12 AxBlack 2022-01-28 05:04:56 UTC 
(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😁.
Comment 13 sh_zam 2022-01-28 11:15:00 UTC 
(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 ... :(
Comment 14 AxBlack 2022-01-28 23:24:19 UTC 
(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? :'(
Comment 15 vanyossi 2022-02-09 05:26:09 UTC 
I tried this on master (08828d1d7b) macos and could not reproduce the issue.
Comment 16 Halla Rempt 2022-02-14 12:21:07 UTC 

*** This bug has been marked as a duplicate of bug 449122 ***