[Feature]: editMacro() Function

[FullBleed]

Describe the Problem

Most of my macros are on lib tokens. And I'm often testing and coding those macros while working on tokens on other maps. So I find myself switching to the working map, testing the macros out, and then switching back to my lib token map, finding the macros (which often need to be scrolled down to in a long list of macros on a token), right-click-editing them, making changes, then going back to the working map testing... rinse and repeat. It's a lot of bouncing around to get access to edit and test the macros.

The Solution you'd like

I'd like to be able to drop a macrolink to an editMacro("macroName@lib:tokenName") function wherever I wanted so that with a single click the editor would open to macros I'm working on and I could make changes without map surfing, finding the macro, right-click-editing, etc. This would significantly speed up development and be a lot less frustrating (especially given the number of small edits that I find myself making during development.)

Alternatives that you've considered.

Drag my lib tokens with the target macros around with me so I can get to them a little quicker... but I'm still scrolling around the libs to find the target macros and right-click-editing them to get into them and make changes.

Additional Context

No response

[Azhrei]

Have you considered opening a second MT instance (as a client) and doing a portion of your editing there? Then you could open multiple macros at once and leave them open in that second instance, while editing one or more other macros on your token...?

[FullBleed]

Have you considered opening a second MT instance (as a client) and doing a portion of your editing there? Then you could open multiple macros at once and leave them open in that second instance, while editing one or more other macros on your token...?

Interesting idea... I could see that working pretty well some times... especially with a multi-monitor setup (which I'm, unfortunately, not using these days.) It would require reconnects if I do anything with onCampaignLoad (or other onLoad events) though... and I'm also not sure what other issues I might run into developing with a server running all the time (for example, the client would need to be a GM client... are there any quirks or limitations of GM clients?) I'm trying to think of times when I've made in-session changes during games that required clients to reconnect... I don't really want to be wondering if something isn't working because of my bad code or because I need to reconnect the client to the server.