ButtonBar eXtended (with macro support)

[Samuel]

Much better!!

Nice to hear that.

What happend if I add a new button to the main button bar?

5. Limitations
- Important: You should not edit the view-ButtonBar directly. On the next switch between edit-ButtonBar and view-ButtonBar the changes will vanish.

Exactly like "jjk" described: You have to create all new buttons in edit-mode.

The problem is that it would be very hard to detect which buttons are new in the view-ButtonBar. Because almost everything could happen: rearrange the order of the buttons, delete buttons, add buttons, change buttons, etc.

If someone has an idea of an easy algorithm I will think of it.

I forgot: personal I don't like to use usercmd.ini. This is for personal use purpose.

To make it possible to use TCs rich parameter possibilities I need either rewrite them all or somehow use TC to call them. (I did a limited rewrite earlier.) Using "em_commands" is currently the only way to do it with TC.
To reduce annoyance I create every entry with the prefix: "em_BBX_"

If TC will support calling of ButtonBar commands I would use that.

Do you have something in mind how to get 100% TC parameter compatibility without "usercmd.ini"?

[Horst.Epp]

....
Do you have something in mind how to get 100% TC parameter compatibility without "usercmd.ini"?

I don't think that usercmd.ini is strictly for personal use.
Its just the way to extend the functions and allows hotkeys to be assigned.
I see no problem with using this for your plugin.

[eugensyl]

Do you have something in mind how to get 100% TC parameter compatibility without "usercmd.ini"?

I prefer to use wcmd_XXX.ini where XXX is language ID before using usercmd.ini . It's the same thing in fact... No special reason.

[Samuel]

How to call a custom command in such a wcmd_XXX.ini? Or should I always rename the old usercmd.ini and copy the file there and then delete it and rename the old file?
This would be worse.

Im not aware of calling a command from an userdefined "*.ini".

[Samuel]

Ok your right.
There is something like: ".\languages\WCMD_DEU.ini"

3 Questions:
1) How to get the current lang postfix?
2) What about the english users do they have something similar?
3) Has this approach no other disadvantages?

[Boofo]

2Boofo:
I added a video, so you can see how easy it works:
ButtonBar eXtended video

IMO its far more userfriendly then the old ini file. You could edit everything from TCs Buttonbar GUI, instead of using an TextEditor with no path completion etc... I believe there will be nothing to confuse you if you saw it once.

I saw the video but I still don't see where I can do multiple commands for the same single button. Or am I missing something from the video?

[Samuel]

2eugensyl:
I answered my own questions by some testings:
1) The filename should be: "%Commander_Path%\Language\WCMD_XXX.INI"
I could get the current "WCMD_XXX.INI" from "wincmd.ini" (entry: LanguageIni=WCMD_DEU.LNG) replacing "LNG" by "ini".

If this entry doesnt exist, then TCs language should be english and I should use. "%Commander_Path%\Language\WCMD_ENG.INI"

2) WCMD_ENG.INI

3) The "WCMD_XXX.INI" is not meant for user commands but it was introduced to be used by custom menu files that should work for every language.

23.07.06 Added: Read em_xyz commands from wcmd_lng.ini (where wcmd_lng is the base name of the selected mnu file) if not found in usercmd.ini, allows custom mnu files with user-defined commands

So perhaps I will make it optional to save the commands there. Making it the default could give trouble to some people using custom menu files.

PS: Its too complicated to get the nam. I think I will make a "ButtonBar eXtended.ini" where an alternative "usercmd.ini" could be specified like:

Code: Select all

Alternative_Usercmd=%Commander_Path%\Language\WCMD_DEU.INI

2Boofo:
I just updated the video with notations:
ButtonBar eXtended video

I hope this makes everything clear. (Macros start at 3:06)

1) You create a group of buttons side by side in "edit-mode". (The buttons are later used as the macro.)
2) Then you give all buttons beside the one to the left the Tooltip: "m"
3) Just go to "view-mode" now and use the button.

[petermad]

2Samuel

2) What about the english users do they have something similar?

Only if they explicitly use wcmd_eng.mnu. Most English users will just use "English" as language and not "English (WCMD_ENG.LNG)" and will therefore NOT be using WCMD_ENG.MNU and hence not WCMD_ENG.INI

So perhaps I will make it optional to save the commands there. Making it the default could give trouble to some people using custom menu files.

You are right - I would not like to have my wcmd_XXX.ini files messed with. But my usercmd.ini I wouldn't mind having changed.

Also - If the user switches between different menus, the wcmd_XXX.ini will also vary - so it is much safer for you to use usercmd.ini - it is always available.

[Samuel]

Thank you for additional explanations petermad.

[eugensyl]

2eugensyl:
I answered my own questions by some testings:
1) The filename should be: "%Commander_Path%\Language\WCMD_XXX.INI"
I could get the current "WCMD_XXX.INI" from "wincmd.ini" (entry: LanguageIni=WCMD_DEU.LNG) replacing "LNG" by "ini".

If this entry doesnt exist, then TCs language should be english and I should use. "%Commander_Path%\Language\WCMD_ENG.INI"

2) WCMD_ENG.INI

3) The "WCMD_XXX.INI" is not meant for user commands but it was introduced to be used by custom menu files that should work for every language.

23.07.06 Added: Read em_xyz commands from wcmd_lng.ini (where wcmd_lng is the base name of the selected mnu file) if not found in usercmd.ini, allows custom mnu files with user-defined commands

So perhaps I will make it optional to save the commands there. Making it the default could give trouble to some people using custom menu files.

PS: Its too complicated to get the nam. I think I will make a "ButtonBar eXtended.ini" where an alternative "usercmd.ini" could be specified like:

Code: Select all

Alternative_Usercmd=%Commander_Path%\Language\WCMD_DEU.INI

Thanks for the answer.
I use and I agree your first edition of button bar extension (toolbar) because:
- it was quite simple to use as utility
- TC behavior it was not altered (button bar)
- it was simple enough to set
- none of TC settings files was altered

Missing (from old style) [my point of view] :
- Only one modifier (Ctrl) was available
- Only internal TC commands (cm_...) can be used (not external em_...)
- Environmental variable indisponible for external executables.

So, why do I have those kind of reactions?
I made a Pack based on TC for Romanian people, but not only, with a lot of settings ready made and I cannot use for example this new extended button bar.
Why?

An old user can have his own usercmd.ini and an upgrade will overwrite this file. Same with Wcmd_XXX.ini.

From my point of view only a distinguish ini file will be interesting for me until now. Don't worry for me. I'm only one.


I'm sorry if you are disappointed.

[Samuel]

Only internal TC commands (cm_...) can be used (not external em_...)

Thats not true. Version 0.3 supported em_commands.

The next update will include the ability to use "Wcmd_XXX.ini". Its almost done, just the docu left.
The next update will also include different actions on the different mouse buttons!

For a pack:
There is actually no need of deliver the "usercmd.ini" bundled. When you install it just call the buttonbar from commandline. (ButtonBar eXtended.exe -c path_to_your_buttonbar).
You dont even need to use it as a buttonbar. You could just access the created em_commands.

I agree its tricky for packs but I think it got much easier to use on daily basis (without need of ini files).

[Boofo]

Thanks for the answer.
I use and I agree your first edition of button bar extension (toolbar) because:
- it was quite simple to use as utility
- TC behavior it was not altered (button bar)
- it was simple enough to set
- none of TC settings files was altered

Missing (from old style) [my point of view] :
- Only one modifier (Ctrl) was available
- Only internal TC commands (cm_...) can be used (not external em_...)
- Environmental variable indisponible for external executables.

I completely agree. That is why I am staying with Toolbar.exe. Even after looking at the video Samuel provided, it still seems too confusing (for us simple laymen) and like too much work to do what Toolbar.exe can do with a simple file edit.

[Samuel]

Did you watch the new video (old video+notes)?
IMO its much clearer.

[Boofo]

For a pack:
There is actually no need of deliver the "usercmd.ini" bundled. When you install it just call the buttonbar from commandline. (ButtonBar eXtended.exe -c path_to_your_buttonbar).
You dont even need to use it as a buttonbar. You could just access the created em_commands.

But you still need to make multiple buttons on a button bar, right?

I agree its tricky for packs but I think it got much easier to use on daily basis (without need of ini files).

INI files are the way of TC, though, so we are used to those by now.

[Boofo]

Did you watch the new video (old video+notes)?
IMO its much clearer.

Yes, sir, it is clearer, but still confusing compared to the Toolbar.exe way.