Hi,
thank you for your attention!
Mach 4 is not Mach 3.
I already read and understood that. I read the threads about feature requests and bug reports ...
I guess, mach3 was coded by using win32 calls, whereas mach4 uses wxwindows.
My thinking does not depend on mach3. I don't know much of it. My thinking comes from other applications / gui systems like java swing or ibm c++ class library ...
I don't know wxwindows, so I don't know, what's possible. Therefore I wrote about what I miss in mach3 and in mach4.
I would suggest reading the API documentation
Yes sir, I already did.
But with the reading, I thought, that the api documentation looks like c++ documentation - and therefor I thought, api docs might be intended for plugin/c++ developers.
No api from c++ level is accessible through lua if you don't create an intermediate function call.
I found the file "LuaCalls", which might be the api-specs for scripting, but looking at the samples, I have no feeling about what needs to be done and what is optional.
Many samples use dialogs. I don't want dialogs. I want most functionality happen in the screen, so that all functions are accessible without mouse interaction.
Thank you very much for the samples in your post. I will go for that.
Respect to what I'm missing in gui: is it possible to add lua-gui-elements to existing panels like notebooktabs or groupboxes?
Then of cause I will have to learn lua and wxwindows.
by the way: when I read about mach4 and lua and wxwindows, my heart started jumping and I thought, so may be the day comes, where machLinux will be available
I'm quite sure, I'm not the only linux guy willing to pay for machLinux.
The reason is that lets the hackers know what to look for to try and disable the timeout!
Hehe - in germany there's a phone company called "O2" - which spends more menpower in disabling functionality than in supporting paying users. Hope you don't follow that direction
P.S.: are you interested in po-file fixes (diffs?)