Re: Another pendant question
Originally Posted by
jwatte
It should be possible to make a patch that works "for almost all new versions."
The trick would be to get some user-installed code to run on start-up, and that code can check whether the patch is installed, and if not, re-apply it, using context patching.
If the patch fails to apply cleanly, because exactly the bit that needs updating has changed, the patch could disable itself and display a message to the user before continuing with an un-patched start.
This all has to happen before the linuxcnc process itself stats up, though, so that the Python code it loads is the patched version after an update.
Just dropping a .desktop file in the startup folder is not sufficient, though, because there's a race condition between which starts sooner, the patcher or the PathPilot.
Pete has that with his pendant. He sends out an update patch to run each time that PathPilot has an update. Or at least he has to check and make sure it's compatible.
The Body Armor Dude - Andrew