Originally Posted by intrusion Actually Bob Pierre is absolutly correct in his statements. I strongly agree
The CamSoft interface can be made to look really cool if you use your imagination. You can create your own bitmapped images for buttons and back ground skins. You can change the color of the Readouts and G-code display window. These are also sizable and positionable through the Design Operator Interface section. |
Ok.. Now see this is exactly what I was talking about.. I just spent 20 minutes getting my axis readout display in the correct place..
Left = 7100 <<Not enough left.. Exit and go back into the setup.exe.. Change to Left = 7200. Start the GUI again.. Ooops.. not enough.. Exit the GUI.. Back into the Setup.exe.. Change to Left=8000.. Start up the GUI again.. Oops.. To much.. Exit the program, Bla bla bla bla...
And as soon as I change screens because I took it home to work on it, it wont be the same and I"ll have to spend another 20 minutes putting that readout display in the upper right corner again... (Ok.. I understand why and that the program wasnt designed to be tranfered back and forth between computer systems with different screen resolutions so I wont say much more about that.. ) BUT, why is it the display windows cant be dragged and re-sized on the fly like every other windows application I have??
Im getting the hang of it slowly.. Also, please understand that as far as CNC interfaces go, I have nothing to compare the camsoft to but other windows programs... Camsoft could be the Sliced Bread of CNC controls and I wouldnt know it because of a lack of reference.
Any other tips for designing??
One thing I have figured out.... where Camsoft falls short, this forum makes up for it.
I wonder why Camsoft does not mention this forum in the user manual for there software?? This place is a great resource for newbies like me...
And another thing, Why is it that the header for the Macros [[Macro1]] is above the code and the header for the Mcodes -----M13 is below the code?? And what is the ----- part of the mcode header for? Is it required as the [[ and ]] in the macro headers?
Ok.. lots of questions but this is more fun then diagnosing encoder / resolver signals.. LOL
Thanks!
Murphy