563
« on: February 18, 2009, 01:23:11 PM »
Good day Jim,
Thanks for taking time to respond. As to why would I want to connect and disconnect in single session, I use my DIY beveller in several modes. As such I write modules that are designed to perform specific tasks ( woodworking tasks like mortise and tenons, box joints, dado's and rabbits. Bamboo rodmaking tasks like mortising reel seats, sawing strips, flaming culms, and of course bevelling individual strips.). Mostly they generate the gcode automatically but I have conceived of several other uses and have modules to perform those tasks. Having to restart Mach each time I want to utilize one of these is a PITA. I could write one master app that does it all but you know how much harder that is to maintain. I guess I could write one that calls dlls for each task and reuses the scripting object but it just would be nice if the com objects would play nice and allow for connecting and disconnecting like you would expect.
Every time I try to do something out of the ordinary I get stymied. I would like to write some new screens but screen4 won't work on the vista64 bit machine that I use for development. Jason's controls are at this time are still limited. My attempts at creating Dll's accessed by VB scripts is fallling short since I can't seem to get access to the main Mach hWnd to allow for new forms/windows.
After 20 years of programming in object pascal I am loathe to pay for another development environment and relearn C++ just for this when I have access to the interface. Even then I don't think you can change plugins on the fly easily (maybe I am missing something here).
Sorry for the rant but it's just one of those days.
RT
PS I have looked at your examples many times and you are to be lauded or your work. I have SDK 2.62 which I think is the last version. My type library generated from mach matches you scriptObject.