Show the index of the button in the tooltip when holding Ctrl or Shift

[Fla$her]

I have experimental toolbars with a bunch of buttons (500+). And when I need to copy the necessary code, I have to first find it in the bar file, and then search for the button for a long time according to ambiguous criteria. If I had seen the index, then the speed of finding would have been reduced tens times.

I understand that my needs may seem specific, but in my opinion, implementing an index display is not some big difficulty. I hope others will also find this useful.

[tuska]

2Fla$her

What do you mean by the index? *)
In your opinion, what steps should be taken in practice to find a button more quickly?

I just counted my buttons: ≈1000 (8 rows, subbutton bars included).

------------------
*) Perhaps a few explanatory words in German would be possible?

[Fla$her]

What do you mean by the index? *)

Each bar file has numbered keys, starting with button№=, cmd№= etc.
If this № will displayed in the tooltip, then after Ctrl+F it's enough for me to set n№= or d№= to quickly go to the desired line.

8 rows, subbutton bars included

It makes no sense to count the rows in the drop-down toolbars, they have their own numbering. This is, consider it, one button.

*) Perhaps a few explanatory words in German would be possible?

If there is something unclear, I will translate it.

[tuska]

OK, thanks - I think I've got it now.

If this № will displayed in the tooltip, then after Ctrl+F
it's enough for me to set n№= or d№= to quickly go to the desired line.

Am I correct in assuming that you then search in the file "default.bar"?

I suppose in the end result this should take place for you:
1. default.bar search for code -> find the button in the buttonbar with the new tooltip (no.)
2. Button with tooltip no. -> find this no. in the default.bar
Is this assumption correct?

8 rows, subbutton bars included

It makes no sense to count the rows in the drop-down toolbars, they have their own numbering. This is, consider it, one button.

I didn't mean the drop-down toolbars here but the buttons I see in front of me when I open TC.

[Fla$her]

Am I correct in assuming that you then search in the file "default.bar"?

Why only default.bar? Any current toolbar.

Is this assumption correct?

The sequence, regardless of the name of the bar file, is correct.

I didn't mean the drop-down toolbars here but the buttons I see in front of me when I open TC.

And why did you write "including"? Have you summed up all the rows of your toolbars?
It was exclusively about the current (displayed) rows. 8-9 rows are occupied by each such toolbar separately.

[tuska]

I support everything here that takes us a step further.
If your suggestion is implemented, a new tooltip should not affect the existing tooltip (max. 259 characters).

However, I have another suggestion on this topic:

1. In the CommandBrowser, one could add a new menu item "Buttonbar".
2. cm_CommandBrowser calls the CommandBrowser
3. Enter the search term in the "Filter" field.
   The contents of the fields "Command", "Parameter", "Start Path" and "Tooltip" can be entered as search terms.
4. The user clicks on the command/search result and then on "OK" or better still double-clicks on the command.
5. Afterwards the "CommandBrowser" window closes and the button in the buttonbar is highlighted in some way.
   With sub-buttonbars, the button can only be highlighted on the visible button.
   In this case, the user must find the button himself in the sub-buttonbar - unless the sub-buttonbar opens automatically
   and the button is highlighted.

[Fla$her]

2tuska
Thanks for the support!

You've come up with a cool idea with button highlighting, of course, but I'm afraid in the general concept of TС development it looks fantastic (not in terms of possibility, but in terms of probability of emergence), given that I couldn't get a little trifle from the author for this dialog..
And here it is also necessary that the current toolbar is automatically selected for this Buttonbar item, because there can be as many of them.

[Fla$her]

Bump for v.11.50

[petermad]

Support++