[Ann-Reply] Reply to Announce group
Yes, the most efficient way(in Windows) is to setup INCLUDE+R3-GUI loader to be executed everytime you click on *.r3 script. I'm using that and every change to the R3GUI sources is then automatically "propagated" once I run any R3GUI script again.
Yes, the strategy Cyphre describes is ideal for immediate testing of any changes made to R3-GUI sources.
Thanks guys - maybe these brief notes could be added to the readme on GitHub.
Adrian, check the new wroding of README, and, eventually, submit a request, please.