We use Practically Macro a lot and it is a great tool! However, the key bindings for custom macros do not work in Juno and Kepler. However, this works fine in Galileo, Helios and Indigo.
In Eclipse, I go to Window->Preferences->Keys, and the custom macro I created shows up under "Command" with the name with which I saved the custom macro. Under "Binding" I choose a keyboard shortcut (and make sure there are no conflicts).
In Juno and Kepler, the custom macros work if I "play" them from the toolbar, but the key bindings do nothing. I raised a bug with Eclipse, but they asked me to contact the PracticallyMacro developer(s) and direct them to that bug...
https://bugs.eclipse.org/bugs/show_bug.cgi?id=407749
We really need this feature, and would much appreciate your help!
Thanks!
Anonymous
Hi, I haven't gotten a chance to try this yet. I assume you are using the latest version (0.4.0)?
Yes, we are using PracticallyMacro v0.4.0
We are also using the Eclipse IDE for C/C++ Developers (not sure if that
matters).
Thanks for looking into this!
Best Regards,
Hari
On Tue, Jun 25, 2013 at 10:46 AM, Ernest ernestpasour@users.sf.net wrote:
Related
Bugs:
#15FYI I have noticed the same issue, however key bindings for the "Play last macro" command, which is automatically added by Practically Macro, do work for me (Juno CDT).
the key binding for Play last macro is done statically, whereas bindings for user-defined commands are done dynamically in code. I believe this is why they behave differently.
It appears that the problem is that with Eclipse 4.x they have moved to the new e4 platform. I will have to do some investigation, but it looks like I have to adjust my code to use the new platform to register commands properly. This might or might not be a simple process.
Thanks again for looking into this!
We are still using Eclipse Indigo to be able to use PracticallyMacro (which we need for our day to day work).
We much appreciate your help!
This would be a great fix for those who are developing on Juno! Many thanks for looking into this.
Very weird. It appears to me that this is an Eclipse bug, but I may have figured out a way to work around the problem. However, it's a bit of a hack, so I'm not sure if it will continue to work in the future or if there might be some bad side effects. Also, I have to use some e4 api, so the plugin will not run in eclipse versions < 4.0.
I've got the code written now so that it should still work on 3.7 Eclipse. However, I'm going to wait at least a couple of days to see if I get a response on the Eclipse bug before I go ahead and push it out. It would not surprise me if my fix fails to work in Eclipse 4.4 or beyond.
Thank you very much for your prompt efforts, the updates and for contacting Eclipse! if you would like, we will be happy to test it for you(the way we use it) in Eclipse 3.7 and 4.3(C/C++ IDE), before you release.
I've put a copy of the jar in the files folder: http://sourceforge.net/projects/practicalmacro/files/experimental/ You should be able to stick this in the dropins directory to try it out.
Probably best to try in a clean Eclipse (without a previous install of Practially Macro)
It works a great on Eclipse 3.7 and 4.3
One small issue I noticed in Eclipse 3.7 is, when you edit a custom macro, the keybindings do not work after the edit, until you restart Eclipse. I have noticed the same with PracticallyMacro 0.4.0, but I forgot to mention it to you earlier. However this is not an issue in Eclipse 4.3 (they may have fixed a bug). This is a not an issue for us (especially since it works in Eclipse 4.3), but I thought I should let you know.
So, as far as we are concerned, PracticallyMacro 0.4.1 seems to work very well for us.
Thanks a lot for your help and efforts - we much appreciate it!
It works a great on Eclipse 3.7 and 4.3
One small issue I noticed in Eclipse 3.7 is, when you edit a custom macro,
the keybindings do not work after the edit, until you restart Eclipse. I
have noticed the same with PracticallyMacro 0.4.0, but I forgot to mention
it to you earlier. However this is not an issue in Eclipse 4.3 (they may
have fixed a bug). This is a not an issue for us (especially since it
works in Eclipse 4.3), but I thought I should let you know.
So, as far as we are concerned, PracticallyMacro 0.4.1 seems to work very
well for us.
Thanks a lot for your help and efforts - we much appreciate it!
From: "Ernest" ernestpasour@users.sf.net
To: "[practicalmacro:bugs] " 15@bugs.practicalmacro.p.re.sf.net
Date: 07/01/2013 05:32 PM
Subject: [practicalmacro:bugs] Re: #15 Keyboard shortcuts do not
work on Eclipse Juno and Kepler
I've put a copy of the jar in the files folder:
http://sourceforge.net/projects/practicalmacro/files/experimental/ You
should be able to stick this in the dropins directory to try it out.
Probably best to try in a clean Eclipse (without a previous install of
Practially Macro)
[bugs:#15] Keyboard shortcuts do not work on Eclipse Juno and Kepler
Status: open
Created: Mon Jun 24, 2013 03:10 PM UTC by mhrj
Last Updated: Mon Jul 01, 2013 04:31 PM UTC
Owner: Ernest
We use Practically Macro a lot and it is a great tool! However, the key
bindings for custom macros do not work in Juno and Kepler. However, this
works fine in Galileo, Helios and Indigo.
In Eclipse, I go to Window->Preferences->Keys, and the custom macro I
created shows up under "Command" with the name with which I saved the
custom macro. Under "Binding" I choose a keyboard shortcut (and make sure
there are no conflicts).
In Juno and Kepler, the custom macros work if I "play" them from the
toolbar, but the key bindings do nothing. I raised a bug with Eclipse, but
they asked me to contact the PracticallyMacro developer(s) and direct them
to that bug...
https://bugs.eclipse.org/bugs/show_bug.cgi?id=407749
We really need this feature, and would much appreciate your help!
Thanks!
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/practicalmacro/bugs/15/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.
Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.
Related
Bugs:
#15Last edit: mhrj 2013-07-03
I have made one more tweak to hopefully future-proof my hack and pushed out version 0.4.2.