QB64.org Forum

Active Forums => QB64 Discussion => Topic started by: Craz1000 on April 25, 2019, 07:58:52 pm

Title: Possible QB1.3 Bug with mouse input
Post by: Craz1000 on April 25, 2019, 07:58:52 pm

seems like _MOUSEMOVEMENTX returns nothing and _MOUSEMOVEMENTY only returns 1 and not -1. Possible bug or did the way _MOUSEMOVMENT is handled change.

Code: QB64: [Select]

1. _FULLSCREEN
2. DO
3.     _LIMIT 10
4.     DO WHILE _MOUSEINPUT
5.         PRINT _MOUSEMOVEMENTX; _MOUSEMOVEMENTY; _MOUSEBUTTON(1); _MOUSEBUTTON(2), _MOUSEX; _MOUSEY
6.     LOOP
7. LOOP UNTIL _KEYDOWN(113) OR _KEYDOWN(81)
8.  

Title: Re: Possible QB1.3 Bug with mouse input
Post by: FellippeHeitor on April 25, 2019, 09:53:54 pm

_MOUSEMOVEMENTX and _MOUSEMOVEMENTY have not ever been fully implemented in stable versions of QB64, having only been available in beta versions prior to 1.0, before the creator decided to integrate QB64 and OpenGL. They simply remained there in a non-functional state - nothing specifically related to the recent 1.3 release, sorry.

Title: Re: Possible QB1.3 Bug with mouse input
Post by: Petr on April 26, 2019, 02:38:02 am

This is my attempt to solve this problem. It's without guarantee, I've only tested it on one computer where the mouse has two axes.

Code: QB64: [Select]

1. DO
2.     D& = _DEVICEINPUT
3.     IF D& THEN
4.         IF _LASTAXIS(D&) >= 2 THEN
5.             IF oldx <> _AXIS(1) THEN
6.                 IF oldx < _AXIS(1) THEN MOUSEMOVEMENTX = 1 ELSE MOUSEMOVEMENTX = -1
7.                 oldx = _AXIS(1)
8.             END IF
9.  
10.             IF oldy <> _AXIS(2) THEN
11.                 IF oldy < _AXIS(2) THEN MOUSEMOVEMENTY = 1 ELSE MOUSEMOVEMENTY = -1
12.                 oldy = _AXIS(2)
13.             END IF
14.         END IF
15.     ELSE
16.         MOUSEMOVEMENTX = 0: MOUSEMOVEMENTY = 0
17.     END IF
18.     PRINT MOUSEMOVEMENTX, MOUSEMOVEMENTY
19.     _LIMIT 50
20. LOOP
21.  

_LIMIT must be used, otherwise is program so fast, that just zeros are displayed.

Title: Re: Possible QB1.3 Bug with mouse input
Post by: Craz1000 on April 26, 2019, 09:27:18 am

Quote from: FellippeHeitor on April 25, 2019, 09:53:54 pm

_MOUSEMOVEMENTX and _MOUSEMOVEMENTY have not ever been fully implemented in stable versions of QB64, having only been available in beta versions prior to 1.0, before the creator decided to integrate QB64 and OpenGL. They simply remained there in a non-functional state - nothing specifically related to the recent 1.3 release, sorry.

That is really odd then. Because in the game I just released I used them and they worked fine? Here is the mouse input section.

Code: QB64: [Select]

1.        DO WHILE _MOUSEINPUT
2.             IF Player1.Locked = 0 THEN
3.                 IF _MOUSEMOVEMENTX > 0 THEN
4.                     Player1.PosX = Player1.PosX + Player1.Speed
5.                     IF Player1.PosX > Settings.RezX THEN Player1.PosX = Settings.RezX
6.                 END IF
7.  
8.                 IF _MOUSEMOVEMENTX < 0 THEN
9.                     Player1.PosX = Player1.PosX - Player1.Speed
10.                     IF Player1.PosX < 5 THEN Player1.PosX = 5
11.                 END IF
12.  
13.                 IF _MOUSEMOVEMENTY > 0 THEN
14.                     Player1.Frame = 3
15.                     Player1.PosY = Player1.PosY + Player1.Speed
16.                     IF Player1.PosY > Settings.RezY - 20 THEN Player1.PosY = Settings.RezY - 20
17.                 END IF
18.  
19.                 IF _MOUSEMOVEMENTY < 0 THEN
20.                     Player1.Frame = 2
21.                     Player1.PosY = Player1.PosY - Player1.Speed
22.                     IF Player1.PosY < 0 THEN Player1.PosY = 0
23.                 END IF
24.  
25.                 IF _MOUSEBUTTON(1) = -1 THEN TIMER(FireLazarTimer) ON
26.                 IF _MOUSEBUTTON(1) = 0 THEN TIMER(FireLazarTimer) OFF
27.  
28.                 IF _MOUSEBUTTON(2) AND DisableLaserInput = 0 AND Player1.SLaser > 0 THEN
29.                     DisableLaserInput = 1
30.                     Player1.Locked = 1
31.                     Player1.SLaser = Player1.SLaser - 1
32.                     CALL SetupSprite(Player1.PosX + 150, Player1.PosY + 5, 0, 0, "SLase", 80, 0, 0, 1, 0, 1, 1, 0)
33.                 END IF
34.             END IF
35.         LOOP
36.  

Title: Re: Possible QB1.3 Bug with mouse input
Post by: FellippeHeitor on April 26, 2019, 09:45:30 am

Was that in v1.2?

Title: Re: Possible QB1.3 Bug with mouse input
Post by: Craz1000 on April 26, 2019, 10:22:03 am

The file name was "qb64_2018-02-12-19-30-35_1d0f920-master_win.7z"

looks like i downloaded it on 10-28-2018

Title: Re: Possible QB1.3 Bug with mouse input
Post by: FellippeHeitor on April 26, 2019, 10:39:06 am

Code: QB64: [Select]

1. DO
2.     CLS
3.     PRINT player1.posx
4.     PRINT player1.posy
5.  
6.     DO WHILE _MOUSEINPUT: LOOP
7.     IF _MOUSEMOVEMENTX > 0 THEN
8.         player1.posx = player1.posx + 1
9.     END IF
10.  
11.     IF _MOUSEMOVEMENTX < 0 THEN
12.         player1.posx = player1.posx - 1
13.     END IF
14.  
15.     IF _MOUSEMOVEMENTY > 0 THEN
16.         player1.posy = player1.posy + 1
17.     END IF
18.  
19.     IF _MOUSEMOVEMENTY < 0 THEN
20.         player1.posy = player1.posy - 1
21.     END IF
22.  
23.     _DISPLAY
24.     _LIMIT 30
25. LOOP

Does the above produce any results on your machine?

Title: Re: Possible QB1.3 Bug with mouse input
Post by: Petr on April 26, 2019, 10:53:11 am

Hi Fellippe. Your code do nothing under QB 1.3 for me, BUT i found QB64 version, which work correctly with _MOUSEMOVEMENTX and _MOUSEMOVEMENTY. Its V 1.1? QB64.EXE date is 09.02.2017 (DDMMYY), filesize is 7.654.912

After rewriting your source as this:

Code: QB64: [Select]

1. DO
2.     CLS
3.     PRINT player1.posx, _MOUSEMOVEMENTX
4.     PRINT player1.posy, _MOUSEMOVEMENTY
5.  
6.     a = _MOUSEINPUT
7.     IF _MOUSEMOVEMENTX > 0 THEN
8.         player1.posx = player1.posx + 1
9.     END IF
10.  
11.     IF _MOUSEMOVEMENTX < 0 THEN
12.         player1.posx = player1.posx - 1
13.     END IF
14.  
15.     IF _MOUSEMOVEMENTY > 0 THEN
16.         player1.posy = player1.posy + 1
17.     END IF
18.  
19.     IF _MOUSEMOVEMENTY < 0 THEN
20.         player1.posy = player1.posy - 1
21.     END IF
22.  
23.     _DISPLAY
24.     _LIMIT 30
25. LOOP
26.  

it then work in the OLD ide correctly, in 1.3 it show Y axis, but badly.

Title: Re: Possible QB1.3 Bug with mouse input
Post by: Craz1000 on April 26, 2019, 12:57:43 pm

Changed it to this. Game was ported to QB64-1.3 just now

Code: QB64: [Select]

1.         DO WHILE _MOUSEINPUT
2.             IF Player1.Locked = 0 THEN
3.                 IF _MOUSEX > Player1.PosX THEN
4.                     Player1.PosX = Player1.PosX + Player1.Speed
5.                     IF Player1.PosX > Settings.RezX THEN Player1.PosX = Settings.RezX
6.                 END IF
7.  
8.                 IF _MOUSEX < Player1.PosX THEN
9.                     Player1.PosX = Player1.PosX - Player1.Speed
10.                     IF Player1.PosX < 5 THEN Player1.PosX = 5
11.                 END IF
12.  
13.                 IF _MOUSEY > Player1.PosY THEN
14.                     Player1.Frame = 3
15.                     Player1.PosY = Player1.PosY + Player1.Speed
16.                     IF Player1.PosY > Settings.RezY - 20 THEN Player1.PosY = Settings.RezY - 20
17.                 END IF
18.  
19.                 IF _MOUSEY < Player1.PosY THEN
20.                     Player1.Frame = 2
21.                     Player1.PosY = Player1.PosY - Player1.Speed
22.                     IF Player1.PosY < 0 THEN Player1.PosY = 0
23.                 END IF
24.  
25.                 IF _MOUSEBUTTON(1) = -1 THEN TIMER(FireLazarTimer) ON
26.                 IF _MOUSEBUTTON(1) = 0 THEN TIMER(FireLazarTimer) OFF
27.  
28.                 IF _MOUSEBUTTON(2) AND DisableLaserInput = 0 AND Player1.SLaser > 0 THEN
29.                     DisableLaserInput = 1
30.                     Player1.Locked = 1
31.                     Player1.SLaser = Player1.SLaser - 1
32.                     CALL SetupSprite(Player1.PosX + 150, Player1.PosY + 5, 0, 0, "SLase", 80, 0, 0, 1, 0, 1, 1, 0)
33.                 END IF
34.             END IF
35.         LOOP
36.  

Title: Re: Possible QB1.3 Bug with mouse input
Post by: TempodiBasic on April 27, 2019, 09:34:03 am

Here my feedback

I've got these results:
noone works
  [ This attachment cannot be displayed inline in 'Print Page' view ]    [ This attachment cannot be displayed inline in 'Print Page' view ]    [ This attachment cannot be displayed inline in 'Print Page' view ]  

Title: Re: Possible QB1.3 Bug with mouse input
Post by: Craz1000 on April 27, 2019, 11:21:05 am

The middle one is the version i was using before i switched to 1.3

Title: Re: Possible QB1.3 Bug with mouse input
Post by: Petr on April 27, 2019, 02:27:03 pm

Yeah, ok, is better see version info.... So QB64, which is work right with my repaired version original from Fellippe is this:

Title: Re: Possible QB1.3 Bug with mouse input
Post by: Petr on April 27, 2019, 02:36:17 pm

And also version 1.1 revision 20170120/51 works correctly with my version. There can not be row "DO WHILE _MOUSEINPUT: LOOP" but "a = _MOUSEINPUT" to work.

With row contains "DO WHILE _MOUSEINPUT: LOOP" it work not under all versions.

Text Only | Text with Attachments