Open lipkau opened 7 years ago
waiting on UI element "button" https://github.com/ewerybody/a2/issues/123
You want the button only to open the Snip folder? Ah no: also to make the connection... hmmm. well. That needs elevation, right? You could provide this function with a ahk snippet too which is called from the button.
I actually want to make all the path elements be able to open up the given location in Explorer or whatever file browser you use...
Most of the association is done in the HKCU, so no elevation required. However, if elevated, some additional associations are created. The button in the path element, to open the folder, would be awesome
Registering a type like .snip
is done in HKCR right? how would you connect it in HKCU only?
How do I go about to execute a ahk snip from the button?
you can see the keys needed in HKCU here: https://github.com/lipkau/ol.modules/blob/develop/dynSnips/dynSnip.ahk#L189
Cool I didn't even know HKCU\Software\Classes!!! 👍
A little tricky at the moment. But we can easily extend the features that are piped into the globals of the buttons exec
. See.
So far when you do:
from pprint import pprint
pprint(globals())
as the button code. You can see whats there. Only thing extra fed in is a2path
. Unfortunately also inconsistent with the module_path
I extended the label with :/
I can make a function available like ahk.call_ahk() Just working locally... call_local_ahk() ?
Features:
icon.ico
) in the folder structure.snip
file extension with a text editornotepad.exe