New Version: 2.1.14181 (2018 10 16)
|
04-13-2020, 12:55 AM
(This post was last modified: 04-13-2020 01:01 AM by Jacob Wall.)
Post: #53
|
|||
|
|||
RE: New Version: 2.1.14181 (2018 10 16)
(04-12-2020 09:37 PM)Eric Rechlin Wrote: I looked into this, and the lack of STRING isn't the issue at all. I added the call to STRING as you suggested, and it had no effect. This is only a problem with the "r" variable here; substitute for any other variable that's defined here (like a, b, c, d, etc) You're correct, it has nothing to do with the lack of STRING, I remember being surprised that it worked, however it was my lack of understanding at the time of object types in PPL. I looked at this again now, and the issue is the use of IFERR when combined with CAS commands. Take this example: Code: EXPORT slk3() Run it as is and should show the distance in each of the three MSGBOX instances, then un-comment the line with IFERR which has a divide by zero error on purpose. I think the first time running with that line un-commented will still work, but then something happens and the next run and you'll see just 'r' in the second and third MSGBOX, which follow the CAS commands. If no errors get triggered by IFERR, then everything should be just fine. My workaround for this was to just write my own PPL commands to substitute for the CAS commands I was using, there was no other solution that I found because the IFERR in my case was to catch a ON key press. Related topic https://www.hpmuseum.org/forum/thread-10995.html |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)