TheIndustriousRabbit
/
amos-professional
1
0
Fork 0
Code Issues 31 Pull Requests Packages Projects Releases Wiki Activity

AMOS Baisc: Limit Mouse produces wrong (strange!) limits #5

New Issue
Open
opened 2023-03-25 15:36:45 +00:00 by john · 0 comments
john commented 2023-03-25 15:36:45 +00:00
Owner
Copy Link

Ref 1.07

Sometimes when you use Limit Mouse using either
Limit Mouse X1,Y1 To X2,Y2
or
Limit Mouse
it can cause a bug in AMOS Pro where the mouse is not limited correctly - the mouse refuses to go
beyond halfway across the screen to the right, regardless of the values used for X1 and X2. If the
mouse is moved upwards off the top of the screen to a certain point it appears at the bottom of the
screen and doesn't move left or right, though it will disappear if you move the mouse downwards and
reappear correctly at the top of the screen!
The fix for this is to use Limit Mouse _SCREEN_NUMBER before you use Limit Mouse with specific
coordinates. Here's an example
Limit Mouse 0
Limit Mouse 128,50 To 128+319,296 : Rem hardware coords used to set limits as 0,0 to 319,246
Tested With
AMOSPro V2.00 uncompiled - has the bug
AMOSPro V2.00 compiled - not tested yet
AMOS V1.36 uncompiled - not tested yet
AMOS V1.36 compiled - not tested yet
Credits

Ref 1.07 Sometimes when you use Limit Mouse using either Limit Mouse X1,Y1 To X2,Y2 or Limit Mouse it can cause a bug in AMOS Pro where the mouse is not limited correctly - the mouse refuses to go beyond halfway across the screen to the right, regardless of the values used for X1 and X2. If the mouse is moved upwards off the top of the screen to a certain point it appears at the bottom of the screen and doesn't move left or right, though it will disappear if you move the mouse downwards and reappear correctly at the top of the screen! The fix for this is to use Limit Mouse _SCREEN_NUMBER before you use Limit Mouse with specific coordinates. Here's an example Limit Mouse 0 Limit Mouse 128,50 To 128+319,296 : Rem hardware coords used to set limits as 0,0 to 319,246 Tested With AMOSPro V2.00 uncompiled - has the bug AMOSPro V2.00 compiled - not tested yet AMOS V1.36 uncompiled - not tested yet AMOS V1.36 compiled - not tested yet Credits * Bug discovered by Lonewolf10 sometime before 2012 * Bug tested/described by Lonewolf10 on 27 October 2012 http://www.amigacoding.com/index.php?title=AMOS:Bug_Limit_Mouse&oldid=4490
john added the
AMOS Pro Bugs List
 label 2023-03-25 15:36:45 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
Labels
Clear labels   
AMOS Pro Bugs List

From the PDF distributed with AMOS Pro 2.10

No Label
AMOS Pro Bugs List
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: TheIndustriousRabbit/amos-professional#5
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?