@TaskMaster
Yes of course that makes sense and i understand that, but gave the explanation above just to let you know, you can do something about from Logic Gui.
The problem i see when transferring code from BLIde to Logic Gui might be that you coded no static values. Like:
CreateWindow:TGadget(name$,x,y,w,h,group:TGadget,style)
or
CreateWindow:TGadget(“”,((x/2)*percentage)/100,y,w,h,group:TGadget)
So where is the position of the window, what is the title? Who can say what is actually inside those variables? Or even worse when you start using formulas. What is the exact value now? You need to compile...
I can write a parser for MaxGui commands but this would solve only a small part of the problem, because what happens to the eventqueue and functions called by an event. While all this is no problem when it stays intact in Logic Gui and calling an editor (as it is now), it could be a huge problem the other way round. Could be interesting what the BLIde SDK can do about it.
Yes of course that makes sense and i understand that, but gave the explanation above just to let you know, you can do something about from Logic Gui.
The problem i see when transferring code from BLIde to Logic Gui might be that you coded no static values. Like:
CreateWindow:TGadget(name$,x,y,w,h,group:TGadget,style)
or
CreateWindow:TGadget(“”,((x/2)*percentage)/100,y,w,h,group:TGadget)
So where is the position of the window, what is the title? Who can say what is actually inside those variables? Or even worse when you start using formulas. What is the exact value now? You need to compile...
I can write a parser for MaxGui commands but this would solve only a small part of the problem, because what happens to the eventqueue and functions called by an event. While all this is no problem when it stays intact in Logic Gui and calling an editor (as it is now), it could be a huge problem the other way round. Could be interesting what the BLIde SDK can do about it.