Home
JAQForum Ver 24.01
Log In or Join  
Active Topics
Local Time 14:35 27 Nov 2024 Privacy Policy
Jump to

Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me.

Forum Index : Microcontroller and PC projects : Does MM care about keyboard type?

     Page 3 of 3    
Author Message
Geoffg

Guru

Joined: 06/06/2011
Location: Australia
Posts: 3194
Posted: 03:47am 03 Apr 2013
Copy link to clipboard 
Print this post

  Grogster said  Press [E] as the first letter of "edit" to run the editor
RUN shows up on the screen as soon as I press [E].

That sounds as if [E] is being interpreted as a function key which has been setup to generate RUN when pressed. [E] is 45 hex and [F5] is 95 hex, so if some bits were received incorrectly that could account for what you saw.

Geoff
Geoff Graham - http://geoffg.net
 
Grogster

Admin Group

Joined: 31/12/2012
Location: New Zealand
Posts: 9308
Posted: 04:43pm 14 Apr 2013
Copy link to clipboard 
Print this post

Is there any way to disable the function key ability so that I can rule this out as a possible cause of the problems?
Smoke makes things work. When the smoke gets out, it stops!
 
TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 6099
Posted: 05:47pm 14 Apr 2013
Copy link to clipboard 
Print this post

I think the problem is more likely to be something being confused with the up-arrow which would give you the last command line.
The up=arrow is converted to chr$(128) which might be easy to get in error.

To eliminate the function keys, try setting them all to something simple.

Jim
VK7JH
MMedit   MMBasic Help
 
Grogster

Admin Group

Joined: 31/12/2012
Location: New Zealand
Posts: 9308
Posted: 09:40pm 14 Apr 2013
Copy link to clipboard 
Print this post

Okey dokey, I will set all function keys to numbers(ASCII numbers, that is), just to eliminate them from the equation.

Edited by Grogster 2013-04-16
Smoke makes things work. When the smoke gets out, it stops!
 
Grogster

Admin Group

Joined: 31/12/2012
Location: New Zealand
Posts: 9308
Posted: 02:34pm 22 Apr 2013
Copy link to clipboard 
Print this post

Quick followup question about these issues:

- I am using the F1-F12 keys in "Normal" mode within my program, to allow the user to make choices: "Press [F1] to continue..." kind of thing.

This is working just fine 90% of the time, but when I get these issues with the KB, I am wondering if it is to do with my choice of using the function keys.

I would think not, but I thought it would be a good idea for me to ask here, in case.

I have disabled the function keys with the likes of OPTION F1 "1" kind of thing for all twelve keys, and will now chnage the menu code for a few menu screens for a start, just to see if this helps things.
Smoke makes things work. When the smoke gets out, it stops!
 
     Page 3 of 3    
Print this page


To reply to this topic, you need to log in.

© JAQ Software 2024