Thanks for your kind words, David.
I'm perplexed by the digitizer sluggishness that you report. On my H3650, when I enable the screen tap sound effect, the difference between the tap sound and the display update in imperceptible. I can tap as fast as my hand can move and there is no lag on *digit entry*. If I rapidly use the roll-down (Rv) button with the stack loaded with values that fill the display I can detect a slight lag.
It occurs to me that a lag in *function execution* might be due to the StrongARM binary running on your XScale processor. I've read that SA code can run slowly but I've not found a description of what runs more slowly.
I did build a new binary yesterday that fixed a double-tap issue. If you're running 0.300, please download 0.302 and try it again. That will eliminate that issue as a possible explanation.
If you have the time and patience to work with me on this, perhaps you could drop me an email and we'll take it out of the forum.
BTW, I didn't know about the commercial sim. Thanks for the heads-up. I'm still contemplating how I might use the On button--which is why it's just a place-holder. I like the shifted idea; what do they use it for when it's not shifted? The stack display is a good idea too.
Cameron
HP-16C site