481
Finished Plugins for Download / Re: Mach MAD Plug in (Maintenance and Diagnostics)
« on: January 25, 2010, 01:06:38 PM »
Scott -
Yea, customers: the source of all problems in a business ;-) - Take the lack of feedback as a good thing <grin> - you know how it is with people (myself included) - we complain about things we don't like, tend to ignore the things we do.
So here is some more feedback: MachMad is the a very handy tool. I'm working on a V4 screen set (Prototype being done on V3) and I use MachMad all the time in the process. I am always using the VB window to run a 3-4 line test of something to figure out what mach is really doing (as opposed to what a doc says it might do) - it's much easier than opening an editor & creating a button etc.
Here is a feature I'd love to have - but I suspect it may not be possible external to mach itself...
The problem: The lack of common IDE features makes debugging mach VB code a real pain - it feels like a nostalgic exercise in using early '70's programming tools. Thankfully, the Cypress VB embedded in mach provides breakpoints, but it offers no way to monitor or change variable values while debugging.
The wish: I'd love to have a way to monitor VB variables (I use MM to monitor Mach DRO, LEDS etc) - but I suspect that being able to do that requires you to be inside the interperter.
BTW- my understanding of the current plan is that while the V3/V4 plugins are different, the V3/V4 macros will be able to coexist on V4. V4 VB code will use a directive up front to tell mach the macro is (all) v4 code calls. Existing VB macros (really any macro w/o the directive) will be interpreted as V3 calls.
Dave
Yea, customers: the source of all problems in a business ;-) - Take the lack of feedback as a good thing <grin> - you know how it is with people (myself included) - we complain about things we don't like, tend to ignore the things we do.
So here is some more feedback: MachMad is the a very handy tool. I'm working on a V4 screen set (Prototype being done on V3) and I use MachMad all the time in the process. I am always using the VB window to run a 3-4 line test of something to figure out what mach is really doing (as opposed to what a doc says it might do) - it's much easier than opening an editor & creating a button etc.
Here is a feature I'd love to have - but I suspect it may not be possible external to mach itself...
The problem: The lack of common IDE features makes debugging mach VB code a real pain - it feels like a nostalgic exercise in using early '70's programming tools. Thankfully, the Cypress VB embedded in mach provides breakpoints, but it offers no way to monitor or change variable values while debugging.
The wish: I'd love to have a way to monitor VB variables (I use MM to monitor Mach DRO, LEDS etc) - but I suspect that being able to do that requires you to be inside the interperter.
BTW- my understanding of the current plan is that while the V3/V4 plugins are different, the V3/V4 macros will be able to coexist on V4. V4 VB code will use a directive up front to tell mach the macro is (all) v4 code calls. Existing VB macros (really any macro w/o the directive) will be interpreted as V3 calls.
Dave