A bug or issue of _FULLSCREEN: it doesn't work to put OFF itself

[TempodiBasic]

Hi
guys and gals of QB64 world.
Today I have got an issue with _FULLSCREEN and I want to share this my bad experience with you to:

1 find the logical error that let me use in a bad way _keywords
2 confirm the issue/feature towards _Fullscreen OFF command that works alternatively using my code below

Code: QB64: [Select]

1. Screen _NewImage(300, 300, 32)
2. waitScreen
3. winX = _DesktopWidth / 2
4. winY = _DesktopHeight / 2
5. _ScreenMove winX, winY
6.  
7. Do
8.     Locate 1, 1: Print " Hit bar space key to move mouse and m to quit"
9.     k$ = LCase$(InKey$)
10.     If k$ = " " Then
11.         DMouseX = (Rnd * winX) + 100
12.         DmouseY = (Rnd * winY) + 100
13.         MoveDesktopMouse DMouseX, DmouseY
14.         Print " we move mouse pointer at "; DMouseX; " "; DmouseY
15.     End If
16.     _Limit 20
17. Loop Until k$ = "m"
18. End
19.  
20. Sub MoveDesktopMouse (x As Integer, y As Integer)
21.     _ScreenHide
22.     _FullScreen
23.     _MouseMove Int((x * 300) / _DesktopWidth), Int((y * 300) / _DesktopHeight)
24.     waitScreen
25.     _FullScreen Off
26.     _ScreenShow
27. End Sub
28.  
29. Sub waitScreen
30.     Do While Not _ScreenExists: Loop
31. End Sub
32.  

3 solve the issue without claim a bad working of the keywords used in this code.

Thanks
for feedbacks
for reading this post
for trying this code posted
for spent your time on this thread

Happy Coding

[Cobalt]

3 solve the issue without claim a bad working of the keywords used in this code.

Its a Bad Working of the Keywords you used in this code! XD

you need
_FULLSCREEN _OFF
not
_FULLSCREEN OFF

your missing the `_`
add it before the OFF and see if it works then.

but I guess according to Fellippe, it shouldn't matter but give it a try anyhow.
It does work both ways on my side though. Screen gets big, screen gets small back and forth.

[TempodiBasic]

Hey boys and girls of QB64
you're fantastic

you have found more than I have seen

1. my Typo error ( so I can correct and improve me!)
2. Parser error (it accepts OFF after _FULLSCREEN  when in syntax is possible _OFF)
3. bad working of keyword _FULLSCREEN  _OFF
 I can see only great and thanks!
 

[FellippeHeitor]

No parser error. Both _OFF and OFF are valid with _FULLSCREEN and _ALLOWFULLSCREEN, as pointed out by Cobalt above.

[TempodiBasic]

thanks Fellippe
so the issue is under the _FULLSCREEN code
because after correcting my typo error the code must be work. But for now it still is giving a different alternate result.

[Cobalt]

What results are you getting?  On my end the program starts in a window then goes full screen then goes back to window and so forth.

[SMcNeill]

What results are you getting?  On my end the program starts in a window then goes full screen then goes back to window and so forth.

Does _FULLSCREEN OFF work on Linux?  It may be a specific OS problem.

[TempodiBasic]

@SMcNeill
Hi Steve, no this is the original result (bug/feature) of _FULLSCREEN 
in the first version the beaviour described by Cobalt has been reached using the statement _FULLSCREEN OFF
then Cobalt pointed me that in the wiki there is _OFF and not OFF  with no difference in result!
(it is right to use _OFF following the wiki but why does Parser accept OFF without error? In more talking with Cobalt and Fellippe I have learnt that for _FULLSCREEN it is possible OFF and _OFF with the same result)
So the question standing up is why does _FULLSCREEN work alternatively?

here the code where _FULLSCREEN has been used

Code: QB64: [Select]

1. Sub MoveDesktopMouse (x As Integer, y As Integer)
2.     _ScreenHide
3.     _FullScreen
4.     _MouseMove Int((x * 300) / _DesktopWidth), Int((y * 300) / _DesktopHeight)
5.     waitScreen
6.     _FullScreen Off
7.     _ScreenShow
8. End Sub

I have tried with no changement of results
  1.  to use a loop with _SCREENEXISTS after _FULLSCREEN alone and then also after _FULLSCREEN _OFF
  2.  to use a _DELAY .2 before _FULLSCREEN alone and then also after _FULLSCREEN _OFF
so it seems to be not related to the action of draw the window surface because SCREEN of window is avaiable.
There is a limit to change from ON/OFF Fullscreen but only going to see below deck it can be clear the cause of working at alternate current.

[SMcNeill]

Seems to me that _FULLSCREEN OFF won't work with the screen show/hide settings.

THIS  works:

Code: [Select]

SUB MoveDesktopMouse (x AS INTEGER, y AS INTEGER)
    _SCREENHIDE
    _FULLSCREEN
    _MOUSEMOVE INT((x * 300) / _DESKTOPWIDTH), INT((y * 300) / _DESKTOPHEIGHT)
    waitScreen
    _SCREENSHOW
    _FULLSCREEN OFF
END SUB
EDIT:  The above works sometimes.  Sometimes it doesn't...  There seems to be a race condition at work here, where sometimes _FULLSCREEN OFF works and sometimes it doesn't.   I don't think it'll be that simple to sort this issue out after all....

[FellippeHeitor]

Maybe it's also a case of evaluating whether you really need to be doing what that SUB is doing anyway.

[TempodiBasic]

@FellippeHeitor
It is clear that the code is an attemp to use QB64 keywords to their limit because is not so  good practice  to stretch keywords.
The goal was to use mousemove on the window fullscreen  and then leave  the mouse there while the window comes back to its original position and  dimensions.

But  this thread is about the occasional finding  of  fullscreen alternate working.

Reading in lbqb.cpp the fullscreen sub is clear and plain. So I have asked to myself  "what is it controlling sub_fullscreen output? " There is one if in that sub to save CPU to draw again if the status of window is already  that  called to draw.
So  I can imagine that the variable of status of window is not adjourned  between the 2 call of fullscreen.

Please be carefull this is only  a my curiosity  looking  into QB64 structure.
Thanks for tip.