Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Key Macros plugin

<< < (6/8) > >>

Mad Scientist:
*how about an option to enable or disable macros from activating other macros

*also changing it so when modifier keys are used to activate a plugin they do not need to be released for the macro to be used

eg currently if you use Alt - 0 you must release both the alt key and the '0' key where from what I have seen with linux and windows when a modifier key is pressed it does not need to be released eg you press down Alt - 0 and release '0' to activate the key. This would be nice for macros to be done quickly in succession.

Otherwise great plugin should nvr have a missing ")" or "}" again  :D

Pecan:

--- Quote from: Mad Scientist on March 03, 2007, 08:15:01 am ---*how about an option to enable or disable macros from activating other macros

*also changing it so when modifier keys are used to activate a plugin they do not need to be released for the macro to be used

eg currently if you use Alt - 0 you must release both the alt key and the '0' key where from what I have seen with linux and windows when a modifier key is pressed it does not need to be released eg you press down Alt - 0 and release '0' to activate the key. This would be nice for macros to be done quickly in succession.

Otherwise great plugin should nvr have a missing ")" or "}" again  :D

--- End quote ---

I'll put 'em on the todo list.

But I'm not sure this can be done:

--- Quote from: Mad Scientist link=top's ic=4681.msg41361#msg41361 date=1172906101 ---*how about an option to enable or disable macros from activating other macros

--- End quote ---
I'd have to parse the user's keymac text to determine if it's invoking another keymac, a menu item, a secondary KeyBinding, etc. That's a big piece of work. I'll see what can be done though.

Re: Repeating keymacs:
For now, when you want to repeat a keymac quickly in succession, eg. Alt-0, hold the Alt key and kit 0 as many times as you want, then release the Alt.

The keymac will then repeat rapidly.

Thanks for the suggestions.

Mad Scientist:
I was just thinking if you can send it you could use a null character( '\0' ) to signify the end of a macro and have it removed after it is detected.

Also I was trying to do this macro:{ENTER}{{}{ENTER}{ENTER}}{}{UP}{SPACE 2} but every 4th line it adds a tab in when used multiple times in a row and I can't figure out why.

Pecan:

--- Quote from: Mad Scientist on March 03, 2007, 09:04:41 pm ---I was just thinking if you can send it you could use a null character( '\0' ) to signify the end of a macro and have it removed after it is detected.

Also I was trying to do this macro:{ENTER}{{}{ENTER}{ENTER}}{}{UP}{SPACE 2} but every 4th line it adds a tab in when used multiple times in a row and I can't figure out why.

--- End quote ---

That macro is mis-configured. What is "}{}" supposed to be. Isn't that supposed to be {}} ?

Using a hot key of Alt-Shift-I, I cannot get it to show a tab.
What hotkey are you using?

This is what I get when I hit Alt-Shift-I 5 times.


For me, it seems to work. Could you show us what it's doing on your end.
Also, what OS and version are you using.

Pecan:

--- Quote from: Mad Scientist on March 03, 2007, 09:04:41 pm ---I was just thinking if you can send it you could use a null character( '\0' ) to signify the end of a macro and have it removed after it is detected.

Also I was trying to do this macro:{ENTER}{{}{ENTER}{ENTER}}{}{UP}{SPACE 2} but every 4th line it adds a tab in when used multiple times in a row and I can't figure out why.

--- End quote ---

I take that last message back. I seem to be getting the tab event even when I enter that macro sequence by hand.

The editor thinks an "enter" after a "{" should be "tabbed" outward. Must be some .cpp syntax thingie.



Anyway, you can correct the situation by using some judicious {home}'s or +{TAB}'s (shift-tabs). Eg:,
--- Code: ---{ENTER}{{}{ENTER}+{TAB}{ENTER}{}}{UP}{SPACE 2}

--- End code ---

EDIT: 4:17 PM
 It even happens on a .txt file. Also be aware that this editor has some key sequences that you cannot override. They're compiled in.

For example, one user found that Ctrl-W will always, when not using a recent KeyBinder,  close a window even though s/he defined it to be otherwise in a macro/menu item.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version