[SOLVED] Developer tool: "Copy as Python"

[blackwind]

The current method of retrieving an action's corresponding Python code (Ctrl+C) has a number of pitfalls:

1. Why should I have to open another window, paste, and clip out what I need?
2. Why should I have to manually unescape ampersands and other HTML entities escaped by the XML generator?
3. Why should I have to prepend "eg.plugins." to the result?

These could all be resolved with a "Copy as Python" menuitem, perhaps with Shift+Ctrl+C as its shortcut. Such an addition would increase the speed of my workflow immensely. Thoughts?

[Pako]

=> 0.4.1.r1600

[miljbee]

Excellent !

[cfull1]

Very nice.

[jonib]

So I finally needed to use the "Copy as Python" command. Thanks for adding it very useful.

jonib

[blackwind]

A small bug: Copy as Python doesn't work as expected with Python Script objects.

[Pako]

A small bug: Copy as Python doesn't work as expected with Python Script objects.

This is weird.
I tried it just now and no problem I have encountered.
Probably it will depend on the content. Can you please attach a script to which it is a problem?

Pako

[blackwind]

Code: Select all

<?xml version="1.0" encoding="UTF-8" ?>
<EventGhost Version="1610">
    <Action Name="Disable WOW64 Redirection">
        EventGhost.PythonScript(u'import win32file\nwin32file.Wow64DisableWow64FsRedirection()\n')
    </Action>
</EventGhost>

When copied as Python, this is the result:

Code: Select all

eg.plugins.sion="1.0" encoding="UTF-8" ?>
<EventGhost Version="1610">
    <Action Name="Disable WOW64 Redirection">
        EventGhost.PythonScript(u'import win32file\nwin32file.Wow64DisableWow64FsRedirection()\n')

This only applies to Python Scripts -- not Python Commands.

[Pako]

So now it is completely clear.
The bug is not related to Python Script action, but any action that is renamed (its label in the tree is written in italics).
But it is obvious, that it happens most frequently just with Python Script .
You can download the corrected file TreeItem.py.

Pako

[blackwind]

Ah, that's interesting. Yep, Python Scripts are the only actions I ever rename, and I've done so for every single one in my config.

One last thing: I was thinking, wouldn't it make more sense if Python Commands and Scripts copied as their contained code rather than an eg.plugins reference? So, this:

Code: Select all

import win32file
win32file.Wow64DisableWow64FsRedirection()

...rather than this:

Code: Select all

eg.plugins.EventGhost.PythonScript(u'import win32file\nwin32file.Wow64DisableWow64FsRedirection()\n')

I, for one, can't think of any scenario in which I'd want the latter over the former.

[Pako]

Yes, it is a good idea. It's logical.
I thought it would be very simple. But it gave me quite a hard time.
I had received ...

Code: Select all

import win32file\nwin32file.Wow64DisableWow64FsRedirection()

instead of ...

Code: Select all

import win32file
win32file.Wow64DisableWow64FsRedirection()

and long time I could not figure out how to get rid of.
But now it works. Again, you can download the new version of TreeItem.py file.

Pako

[blackwind]

Excellent. I'd recommend removing the trailing " + chr(10)" on both lines so the code that's copied is identical to the code written, but other than that, looks good!