I edit the macro file all the time. Prolly 80% of my macro changes are edits using a plain text editor. Just make sure you are careful, follow the patterns you already see there. When you start out, make a copy.

Copy stuff from either one into the other, but do not paste into the file you are copying from, stick with it to the end. If you are copying from a macro file, you are not corrupting it, so you can always fall back to it. Then you can test the edited file. If you make a mistake, and paste into the "copying from" file, simply close the file without saving, and open it again. Make sure to use an editor that does not save the edits on a regular basis, so if you make a mistake, it won't save it.

Note the numbering scheme, where
// Macro # 1
/$ 0 <<<<<<<< this starts at 0, but the line above starts at 1

73 Rich NE1EE

开云体育

Yeah...
1. This UI is not what we are used to thinking of as Object Oriented Programming, even if it uses objects...I havna looked at the code. But I have extensive software engineering experience, and I can say that just being able to move the buttons around with a mouse requires a step up in programming resources, and by that I mean not just the time to do it, but the software tools to handle it.

2. OTOH, there may be a simpler way to achieve it using current tech. Implement a 'move or copy button' feature. In this case, the user might RMC the button, get a context menu that offers these choices, and selects on. Selecting copy would place the button label and macro in a buffer. RMC a new button, and one of the options is 'paste'. But is that worth the labor? Not my call. A poll of users is needed for the devs to consider it. I admit that early on I wanted that capability, but because I am content with editing a plain text file, I just moved on. I'd surely use this feature if it were available. In fact, such a context menu might then have copy, paste, move, delete. I am not sure why so many are leery of editing a plain text file. If you can write a letter to Mom, you can edit that file. A few simple rules, and, yes, folks, it's just that easy. The context menu discussed here would obviously be much easier, especially for those who find typing difficult.

3. Vet here. I think that it is sad that so many of the unimaginitive sayings of the military have found their way into the every-day lives of civilians. In so many ways, we have lost much culturally. In my youth, I looked forward to now, and imagined how much better off we would all be. Instead, I find that society has, in general, decayed in tangible ways that I experience in every-day life. I find it darkly ironic that a society that has so little regard for the daily lives of its military has adopted, in its ignorance, so many military social customs and slang, to its detriment.

Nonetheless, we all have our opinions, and are free to express them, so I am not flaming Mike.

~R~

I don't feel flamed at all sir....... and -- THANK YOU -- for whatever you did for the country.

For a long time I've thought the nation didn't deserve the honor and dedication people like us brought to the table. I was selected for a very special job, only about 6,000 certified in the USA. Not because of a degree. Not because of training or experience. But because they needed that guy who showed up dead, but still showed up every time. Three years after retirement they were still begging for me to come back.

These days I'm fully retired - spending my days playing with radios and jeeps. And I cannot begin to express how much I appreciate the authors of the wonderful software packages we all use. I can barely spell proggraming right.... I could never do it! So a big THANK YOU to all the folks that bring us FL-Digi, WSJT-X and all the other cool stuff. My retirement would be a lot more boring without the toys to play with.



Vy73 - Mike - KD5KC.
El Paso, Texas - DM61rt.
SOTA W5T-Texas Association Manager.