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

BUG: The "Info" button does not work with the Controller Rack button in the 2nd row #4119

Closed
raindropsfromsky opened this issue Jan 17, 2018 · 10 comments
Labels

Comments

@raindropsfromsky
Copy link

The "i" button does not work with the Controller Rack button in the 2nd row.
(It works with all 6 other buttons. Thus, technically this is a bug, but not worth much.)

In any case the "Info" button seems to be redundant: It does not add any value!
It just shows a tooltip when the mouse is hovered over buttons.
Well, that same tooltip is shown even without clicking on this button first!

It does not work on the other elements of the screen, either. So I guess that it is yet to be implemented fully (?) If so, a suggestion: When the user clicks on the "i" button first, let LMMS show an extended tooltip instead of normal (short) tooltip.

@PhysSong
Copy link
Member

Could you add a screenshot for this issue?

@raindropsfromsky
Copy link
Author

raindropsfromsky commented Jan 17, 2018

Well, as the examples below show, there is no consistency in results:

  1. In some controls, there is a ban symbol, and no tooltip.
  2. In others, there is a ban symbol, but the tooltip is displayed.
  3. In yet others, there is a "?" overlay (instead of the "banned!" icon), and a tooltip is shown

The tooltip is shown even without clicking on the "i" button, so apparently it adds no value.

After clicking on "i" button:
image

Without clicking on "i" button:
image
(The only difference is the "?" overlay on the mouse-pointer.)

After clicking on "i" button:
image
(Note that despite the banned symbol, the tooltip is shown anyway!)

Without clicking on "i" button:
image
(Tooltip is shown.)

After clicking on "i" button:
image
(Banned symbol, and no tooltip.)

After clicking on "i" button:
image
(Banned symbol, and no tooltip.)

After clicking on "i" button:
image
(Banned symbol, and no tooltip.)

After clicking on "i" button:
image
(Despite the banned symbol, the tooltip is shown anyway!)

@raindropsfromsky
Copy link
Author

raindropsfromsky commented Jan 17, 2018

BTW there is yet another problem:
Normally, after clicking on the "i" button, we can hover the mouse over multiple controls, and it goes on showing their tooltips. But if I hover over the "notes" area, and then move the mouse out of the "notes" area, LMMS quits the info mode automatically.

image
There may be other controls that behave in this way.

@Sawuare
Copy link
Member

Sawuare commented Jan 17, 2018

I think we should remove the What's this? system because it's not fully implemented and has bugs.
Tooltips and documentation would be sufficient for teaching users.

@tresf
Copy link
Member

tresf commented Jan 17, 2018

I think we should remove the What's this? system because it's not fully implemented and has bugs.
Tooltips and documentation would be sufficient for teaching users.

I wholeheartedly agree with this. Outside of LMMS, I've never used a help system like this before.

@Sawuare
Copy link
Member

Sawuare commented Jan 17, 2018

I will remove it. What branch should I target, master or stable-1.2?

@tresf
Copy link
Member

tresf commented Jan 17, 2018

@Sawuare it should be properly discussed I think, but master.

@Sawuare
Copy link
Member

Sawuare commented Jan 22, 2018

@tresf What aspect should be discussed? 🤔

Some info:
On master, searching for WhatsThis gives 121 results in 19 files, mostly setWhatsThis() and QWhatsThis::showText() (99 translatable strings), and some code for the functionality itself and its toolbar button.
Edit: The numbers above represent searching in src. When searching in include and plugins, the total numbers are much higher.

@tresf
Copy link
Member

tresf commented Jan 22, 2018

@Sawuare, it's something that we should run past the #devtalk channel first I think.

@Sawuare
Copy link
Member

Sawuare commented Jun 7, 2018

Fixed via #4128.

@Sawuare Sawuare closed this as completed Jun 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants