By the way, I just checked breakpoints and they seemed to work for me. I’m just about to release an update. OnOffsetLeft/right/none will now be just after OnPenDown and just after OnPenUp.
Les, you’re awesome, thank you! And okay, i’ll try the break points again after i update.
I’ve had sporadic trouble with breakpoints in the past when I was developing my post processor. Haven’t messed with it for a while, though.
I’ve had sporadic trouble with breakpoints in the past…
Comforting to know, because i really cannot get them to work now. I was starting to think i was just doing something stupid. Which i still may be.
Les, correct sequence would be open editor, set breakpoint, save, close editor, run post, and it should stop at a break point and display the editor, correct?
Also Les, its a little hard to tell without the breakpoints working, but it appears the OnOffsetNone is not getting called when the operation is set to “No Offset”.
You only need to save if you have made a change. You also don’t need to close the editor. Either way it should work. I just tested it here and it worked as expected with the editor closed or not. By the way there is a run post button in the editor toolbar so you don’t need to switch back to the SheetCam main window.
The only way I have found to break breakpoints is to edit a post supplied with SheetCam (i.e one that is not marked ‘edited’) then try to set breakpoints on it. When you edit a standard post, SheetCam makes a copy in it’s settings folder. Any breakpoints you set however end up matched to the original file name. Restarting SheetCam or closing the file in the editor (File->close current page) then reopening it will fix this. Note: simply closing the editor won’t fix it because close actually just hides the window.
Also Les, its a little hard to tell without the breakpoints working, but it appears the OnOffsetNone is not getting called when the operation is set to “No Offset”.
Ye, that’s likely to happen. It assumes the machine starts with no tool offset applied.
The only way I have found to break breakpoints is to edit a post supplied with SheetCam (i.e one that is not marked ‘edited’) then try to set breakpoints on it.
And voila, that is exactly what was happening to me. Breakpoints work for me now. This is not the first time the saving the edited post to the user AppData folder has caught me with my pants down. Really a good thing to do though.
Ye, that’s likely to happen. It assumes the machine starts with no tool offset applied.
Is that something that may could be modified in the next release? It is not likely to ever cause me a problem, but it could happen. Just with the sequence in the post, it needs to call the OnOffsetNone in order to call the function that writes the start codes.