Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ColorPicker registerForRefresh behavior #31

Open
sirinsidiator opened this issue Sep 15, 2015 · 3 comments
Open

ColorPicker registerForRefresh behavior #31

sirinsidiator opened this issue Sep 15, 2015 · 3 comments
Milestone

Comments

@sirinsidiator
Copy link
Owner

circonian wrote:

If a panel is set to refresh, registerForRefresh= true, the colorPicker fires the setFunc non-stop as the colors are changed, even though the user has not clicked "Accept" to set the color.

If they click "Accept" nothing happens, setFunc does not fire. Which I guess is ok since setFunc was firing as we were changing the colorPicker.
If the user clicks "Cancel" it does fire the setFunc one more time passing it the original color to reset it, although if you hit "Esc" the color gets changed (setFunc was firing as you were changing colors) & it does not fire that final setFunc to revert the color back to the original color because the user did not click "Cancel".

I know its set to register for refresh, but the user hasn't actually changed the color yet. Should setFunc even be firing as the colorPicker changes values? In some ways its nice to see the colors changing as you drag the color picker around, but it also fires setFunc a lot. The slider does not function that way. It doesn't fire setFunc until you stop dragging the slider (which is kind of like clicking accept).

I guess it's not really a huge deal, and may be intentional (except that ESC key thing), but either way I just thought I would let you know.

@sirinsidiator sirinsidiator added this to the r19 (pts 2.1) milestone Sep 15, 2015
@sirinsidiator sirinsidiator modified the milestones: r20, r19 Feb 24, 2016
@sirinsidiator
Copy link
Owner Author

The behavior is caused by the ingame color picker dialog. It's something that needs to be fixed in the client. The set function being called continuously is something that may be worth a config entry on the table, so it can be disabled.

@sirinsidiator sirinsidiator modified the milestones: future, r20 Mar 25, 2016
@A-312
Copy link

A-312 commented Jun 10, 2016

Did you find a fix ?

@sirinsidiator
Copy link
Owner Author

I fixed the color picker bugs in Medic - UI Fixes as it is not really an issue with LAM itself. I have also reported them, but I don't think they have a high priority.

As for the set callback being called before the color is accepted, I am thinking of splitting it into 2 separate functions, so one is called for preview purposes and the other for actually setting the selected color, but it may require a major update as it would break addons that rely on that behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants