by cncdrive » Tue Dec 06, 2016 11:58 pm
Terry,
Changing the #var writting to the Status instead of a popup window is far the most easy of the things you asked about.
All the other things you mentioned requires drastic codes changes.
The expression next to g-codes needs lots of code changes, because now only a variable number and a boolean value about if it is a number or a variable is stored when the # is used with a word and this is done in all codes in the whole interpreter and g-code executer, so if we want to change this then we have to change what we store, we have to store the whole expression string and compile it on runtime which is programmatically not a problem, but it probably takes a few thousands of code lines to be changed both in the interpreter and in the g-code executer.
I think I will make the ?#var first to Status bar, because that one is simple and can be done fast, and will try to implement the .codelong directive and when done will come back to discuss what to do next.
It seems it is better to do the .codelong first, because sooner or later, but I will like to implement that and we already talked about it a long time now with Terry and it seems to be the most complicated and longest code change of all, so I think it would be better to make it asap to let you guys test it and to give it time to mature.