I have an issue with FSLabs A320 where some macro calls result in the button or switch assuming a latched condition. The most annoying one that I've been battling with for months is the Rudder Trim switch. In the VC, a simple left click pulls the button momentarily to the Left, and a right click momentarily to the Right. I record this as a Macro, but then the subsequent execution (in my case a CTRL-Key combo) results in a latched condition. The Rotorbrake codes do the same thing so it's not just my macros. I have (after 15 years of being a FSUIPC user!) finally rolled up my sleeves to see what advanced stuff is lurking in the guides and I'm learning new stuff. If there's any examples, of how to code various click type combos, please can someone/Pete point me to the relevant section? I've played around with various 'on release condition' things too but no change. Any suggestion as to what else I can try?
A couple of other questions whilst I'm here:
1.) If I make a change inside the MACRO file, can I get away with restarting the flight? or must the sim be restarted?
2.) I read somewhere about a method by which FSUIPC logs details about panels/gauges that were clicked with a list of variables available to play with(?). I hope I got that right. Has this concept been depreciated due to the latest version of FSUIPC using 'Rectangles?' What debug methods are available in the latest version? Again a pointer to the relevant section in the guide would be very helpful!