-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Tooltip for channel-names in FX-mixer inconsistent #3321
Comments
I've also noticed some possible odd behaviour there but as you've noticed too it's intermittent. Just acts up when it feels like. |
Oh, good, I don't have to make any screenshots for this issue. :) I also noticed the same issue and eventually noticed at least one reliable cause:
This will result in a FX Channel tool tip with "FX 1" rather than "TripleOscillator" as expected. "Double-clicking on the FX Channel name" and ("hitting enter" or "clicking off the name") will result in the tool tip displaying the correct result. (Which I sometimes do accidentally so hadn't noticed the connection previously.) I've yet to look into the code to see why this happens as I'm also looking into a bunch of other issues but hopefully being able to reproduce the issue is a start. I've also noticed (maybe only once?) the actual channel name and tool-tip being the truncated form with an ellipsis ("...") but it may be unrelated. |
Need a 'Bug'-label |
OS : winXP sp3
LMMS 1.1.90-RC2.8
Issue description:
![tooltipinconsisten01](https://cloud.githubusercontent.com/assets/6662066/22603114/5b7fa192-ea46-11e6-9f0c-12cb01ac1300.JPG)
Displaying FX-channel-names with tool-tip is unpredictable inconsistent
Example :
In both examples, the mouse is over the red dot.
Here the tool-tip only shows FX1 and not the channel-name
![tooltipinconsisten02](https://cloud.githubusercontent.com/assets/6662066/22603156/7dba9eba-ea46-11e6-9084-e1899adcdb79.JPG)
Here the channel-name of the next channel is shown in the tool-tip
I have tried with both new and old projects, and some are fine, some has it messed up
I have no explanation for the behaviour
So far i know:
The text was updated successfully, but these errors were encountered: