Module: dynSnips - Githubissues

lipkau / ol.modules

Modules to extend a2

GNU General Public License v3.0

2 stars 1 forks source link

Module: dynSnips #22

Open lipkau opened 7 years ago

lipkau commented 7 years ago

Features:

[x] manifest contains link to documentation
[x] module has an icon
[ ] module is documented in wiki
[ ] module shows relevant debug messages
[ ] module shows relevant notifications
[x] user can change path to snip folder in a2 UI
[x] user can change the hotkey to trigger the menu
[x] menu supports icons (named icon.ico) in the folder structure
[ ] a2 UI has a button to associate the .snip file extension with a text editor
[ ] user can choose the text editor
[ ] default text editor is notepad.exe
[ ] a2 UI has a button to open the snip folder

lipkau commented 7 years ago

waiting on UI element "button" https://github.com/ewerybody/a2/issues/123

ewerybody commented 7 years ago

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...

lipkau commented 7 years ago

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

ewerybody commented 7 years ago

Registering a type like .snip is done in HKCR right? how would you connect it in HKCU only?

lipkau commented 7 years ago

How do I go about to execute a ahk snip from the button?

lipkau commented 7 years ago

you can see the keys needed in HKCU here: https://github.com/lipkau/ol.modules/blob/develop/dynSnips/dynSnip.ahk#L189

ewerybody commented 7 years ago

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() ?