Post Reply 
(Free42) Bug: GETKEY and stack lift disable
07-03-2020, 02:18 PM
Post: #1
(Free42) Bug: GETKEY and stack lift disable
GETKEY does not honour the stack lift disable (CLX, ENTER, there are others)
iOS Free42 2.5.18
DM42 Free42 2.5.16

Code:
 LBL "T"
 44
 ENTER
 ENTER
 ENTER 
 CLX 
 GETKEY
 END
XEQ "T", press any key will result in
Code:
  42S   Free42
T 44      44
Z 44      44
Y 44       0
X keycode keycode

Cheers, Werner

41CV†,42S,48GX,49G,DM42,DM41X,17BII,15CE,DM15L,12C,16CE
Find all posts by this user
Quote this message in a reply
07-03-2020, 04:12 PM
Post: #2
RE: (Free42) Bug: GETKEY and stack lift disable
Confirmed. I'll fix this in the next release. Thanks!
Visit this user's website Find all posts by this user
Quote this message in a reply
07-05-2020, 06:27 PM
Post: #3
RE: (Free42) Bug: GETKEY and stack lift disable
...and done.

The update for iOS is pending approval so that may take a day or two.
Visit this user's website Find all posts by this user
Quote this message in a reply
07-05-2020, 06:49 PM
Post: #4
RE: (Free42) Bug: GETKEY and stack lift disable
Thanks Thomas!
Werner

41CV†,42S,48GX,49G,DM42,DM41X,17BII,15CE,DM15L,12C,16CE
Find all posts by this user
Quote this message in a reply
07-06-2020, 02:06 AM
Post: #5
RE: (Free42) Bug: GETKEY and stack lift disable
(07-05-2020 06:27 PM)Thomas Okken Wrote:  ...and done.

The update for iOS is pending approval so that may take a day or two.

I notice the bug exists in the DM42 as well. Is this considered serious enough to warrant an update to the DM42?

Tom L

Tom L
Cui bono?
Find all posts by this user
Quote this message in a reply
07-06-2020, 05:24 AM
Post: #6
RE: (Free42) Bug: GETKEY and stack lift disable
(07-06-2020 02:06 AM)toml_12953 Wrote:  I notice the bug exists in the DM42 as well. Is this considered serious enough to warrant an update to the DM42?

I've put it on David's radar.

There are only 10 types of people in this world. Those who understand binary and those who don't.
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: