Hello,

I recently upgraded to PV2.9, and had and issue - the delayed shutdown with ignition key switch does not work, it immediately shuts down.

I was told Patch 1 Beta fixes this, so I tried it. I got about 30 compile errors that I never saw before, on Murphy scripts that I don't use. So I deleted all the scripts and it compiled. I thought all was good as now the ign. key delayed shutdown works.

Unfortunately although that now works, anywhere in the program where I use buttons to change a value on the screen don't work!

This is why I hate upgrading. I should never have upgraded to 2.9.

I have a very unhappy customer as he needs the screen to remain on to calibrate a transmission on a half million dollar agricultural spreader sprayer.

We can probably help you resolve the compile errors in the scripts. Most of the new error messages are caused by variable type conversion. Usually just have to use an int function to change the variable type.
int x = z; // changes to:
int x = int(z); // where z is a double
You can also compare to the scripts in the Murphy Standard configuration in PV2.9 Patch 1 Beta that have been fixed to correct the new errors.

Thanks, but if you read my post I fixed the compile errors by deleting the scripts.

As I said, now anywhere in the program where I used buttons to change values no longer work! All this to try to get the display to stay on after ign. key goes off!

It was my guess that the configuration didn't work because the scripts were deleted.

No, completely unrelated. All the errors were built in scripts that were not being used.

If you can private message the configuration to me we will take a look to see what the problem is with the buttons. Nothing like this has been reported before.

Actually, thinking about it, if a state machine or a script gets in an infinite loop it will prevent any other events from firing that are tied to a button. It can still switch page views but anything that does an event will be hung. You can try changing a button to a Go To View and see if it works. Also, the CPU usage can be checked with the Tools -> Remote Diagnostics Console to see if it is in an infinite loop.