|
Post by jnoblin on Jun 28, 2021 3:43:00 GMT 1
@jos,
I ran into a problem using the mouse with the 20210501 version. When you roll the mouse wheel while waiting for an entry in say, get, read routines, the mouse wheel appears to be giving a tab function that moves to the next or previous field depending on which way you roll the mouse wheel. It does not do this in previous versions.
Let me know if you need a sample program to test this.
Everything else seems to work great.
Thanks, Nob
|
|
|
Post by Jos on Jun 28, 2021 6:47:58 GMT 1
Rolling the mouse wheel up or down is now treated as a Up or Down arrow key press.
That was asked for by some, but I guess you don’t like that?
Jos
|
|
|
Post by jnoblin on Jun 28, 2021 10:12:21 GMT 1
I didn't realize you intended for this to happen. I would prefer the mouse wheel not to act like up and down arrow keys. A lot of my programs are not that sophisticated and will actually finish the procedure if the mouse wheel is rolled down by mistake. Also, the mouse is used to double click memo fields to edit them without having to enter CTRL PAGE UP to edit and then CTRL ENTER to save the memo field if the mouse is disabled.
Would it be a lot of trouble to have the MOUSE command to have the option to not act as Up or Down arrows? MOUSE = ON NOWHEEL or MOUSE = ON NOARROW
Thanks, Nob
|
|
|
Post by Jos on Jun 28, 2021 15:01:31 GMT 1
How real is that mouse wheel mistake and the consequences? (Double) Clicking isn’t effected.
I don’t like to add more options to config.txt, people seemingly already have problems reading that.
Eventually I would opt for a ‘force’ activate the mouse wheel: It won’t do anything unless you once roll the wheel two clicks in the same direction within for instance one second.
Jos
|
|
|
Post by jnoblin on Jun 28, 2021 18:18:16 GMT 1
I would just not use the mouse until when and if I get a chance to go through all the programs to add loops to verify data is okay before leaving each procedure. I am not a professional programmer and wrote these in Foxbase over 30 years ago (then FoxPro). The code is not pretty but it does everything we need to do.
I know double clicking works with mouse on but with mouse off, I would have to have the users tab or arrow to the memo field and use CTRL PGUP to edit and then CTRL ENTER to save the changes. With mouse on, they just double click on the memo field and edit it.
I think the option might help but I would still worry that the users could mistakenly edit an expensive order and leave the procedure with the mouse wheel in my situation.
Bottom line is I can live without the mouse for the new version.
Thanks again for the program and all the support you provide us.
Nob
|
|
|
Post by Jos on Jun 28, 2021 18:32:58 GMT 1
Doesn’t the risk users accidently pressing the Up or Down key equal that of the mouse wheel?
Jos
|
|
|
Post by jnoblin on Jun 28, 2021 23:31:09 GMT 1
Yes, that could happen. We use only desktops computers with full size keyboards which have separated arrow and number sections but it could happen. I will start looking at the most serious programs and make them more bullet proof for use with the mouse.
Thanks Jos,
Nob
|
|