Text Only | Text with Attachments

QB64.org Forum

Active Forums => QB64 Discussion => Topic started by: Omerta7486 on August 02, 2018, 11:27:54 am

Title: Removing the tile bar/glitchy gui code
Post by: Omerta7486 on August 02, 2018, 11:27:54 am
Is there a way to remove the title bar completely from an app frame? I would like to build custom GUIs for my programs, and the title bar gets in the way.

Also, when I use $Checking:OFF the close button[X] on the title bar doesn't function. When you click it, it will visually "click," but it will not close the app window.

And, one last thing. If I use _screenhide to minimize my window, I can't restore the app by clicking it's button on the taskbar. It stays minimized on my taskbar. Is there something I'm missing, or does _screenhide not do what I think it does?

Thanks in advance,

-Omerta
Title: Re: Removing the tile bar/glitchy gui code
Post by: FellippeHeitor on August 02, 2018, 12:10:48 pm
Quote from: Omerta7486 on August 02, 2018, 11:27:54 am
Is there a way to remove the title bar completely from an app frame? I would like to build custom GUIs for my programs, and the title bar gets in the way.
There is currently no native way of doing that in QB64.

Quote
Also, when I use $Checking:OFF the close button[X] on the title bar doesn't function. When you click it, it will visually "click," but it will not close the app window.
It is not recommended to use $CHECKING:OFF an never to turn it back ON. The idea of checking:off is that is disables all event checking - system events like the close button and TIMERS included - for when your program needs to perform an intensive task. But then you should turn it back on, or you get side effects like the one you described.

Quote
And, one last thing. If I use _screenhide to minimize my window, I can't restore the app by clicking it's button on the taskbar. It stays minimized on my taskbar. Is there something I'm missing, or does _screenhide not do what I think it does?
It apparently doesn't do what you think it does. _SCREENHIDE literally hides the screen, which needs to be programmatically shown again with _SCREENSHOW.

What you want is _SCREENICON (http://qb64.org/wiki/SCREENICON) - that's what will minimize the current window.
Title: Re: Removing the tile bar/glitchy gui code
Post by: bplus on August 02, 2018, 01:41:44 pm
Code: QB64: [Select]
  1. _TITLE "Aquarium with swaying kelp"
  2. 'QB64 X 64 version 1.2 20180228/86  from git b301f92
  3.  
  4. CONST xmax = 1260
  5. CONST ymax = 720
  6. CONST swayLimit = 3
  7. CONST maxFish = 1024
  8.  
  9. SCREEN _NEWIMAGE(xmax, ymax, 32)
  11.  

When I use this, there is no title bar displayed, is this a flaw?
Title: Re: Removing the tile bar/glitchy gui code
Post by: FellippeHeitor on August 02, 2018, 01:53:15 pm
Fullscreen won't show a title bar, of course. I understand Omerta wants a borderless window - notice how he talks about removing the title bar from an app frame.
Title: Re: Removing the tile bar/glitchy gui code
Post by: SMcNeill on August 02, 2018, 02:39:46 pm
Quote from: FellippeHeitor on August 02, 2018, 01:53:15 pm
Fullscreen won't show a title bar, of course. I understand Omerta wants a borderless window - notice how he talks about removing the title bar from an app frame.

http://qb64.org/wiki/Windows_Libraries#Borderless_Window   <--- This is how we used to do it, but with _WINDOWHANDLE and such, the process should be a little simpler now, with even fewer DECLARE LIBRARY calls necessary. 
Title: Re: Removing the tile bar/glitchy gui code
Post by: FellippeHeitor on August 02, 2018, 03:04:17 pm
Steve is right! And you can simplify that sample like this:

Code: QB64: [Select]
  1. '============
  2. 'NOBORDER.BAS
  3. '============
  4.  
  6.     FUNCTION GetWindowLongA& (BYVAL hwnd AS LONG, BYVAL nIndex AS LONG)
  7.     FUNCTION SetWindowLongA& (BYVAL hwnd AS LONG, BYVAL nIndex AS LONG, BYVAL dwNewLong AS LONG)
  8.     FUNCTION SetWindowPos& (BYVAL hwnd AS LONG, BYVAL hWndInsertAfter AS LONG, BYVAL x AS LONG, BYVAL y AS LONG, BYVAL cx AS LONG, BYVAL cy AS LONG, BYVAL wFlags AS LONG)
  10.  
  11. GWL_STYLE = -16
  12. WS_BORDER = &H800000
  13.  
  14. _TITLE "No Border"
  16.  
  17. PRINT "Press any key for no border...": A$ = INPUT$(1)
  18.  
  19. winstyle& = GetWindowLongA&(hwnd&, GWL_STYLE)
  20. a& = SetWindowLongA&(hwnd&, GWL_STYLE, winstyle& AND NOT WS_BORDER)
  21. a& = SetWindowPos&(hwnd&, 0, 0, 0, 0, 0, 39)
  22.  
  23. PRINT "Press any key to get back border...": SLEEP
  24.  
  25. winstyle& = GetWindowLongA&(hwnd&, GWL_STYLE)
  26. a& = SetWindowLongA&(hwnd&, GWL_STYLE, winstyle& OR WS_BORDER)
  27. a& = SetWindowPos&(hwnd&, 0, 0, 0, 0, 0, 39)
  28.  
  29. PRINT "The end"
  30.  
  31.  
Title: Re: Removing the tile bar/glitchy gui code
Post by: Omerta7486 on August 02, 2018, 08:50:45 pm
Thank you, Fillippe, BPlus, Steve!

I have a few questions. Both _SCREENICON and _WINDOWHANDLE show up in QB64 as valid commands, but neither has documentation on the wiki, and _WINDOWHANDLE doesn't even have an F1 help page in the IDE! Is there some documentation I am missing?

[EDIT]: Okay, I found their reference under the alphabetical list, but not the usage list. '~' I shall get to studying! Haha. Thank you, all!
Title: Re: Removing the tile bar/glitchy gui code
Post by: bplus on August 03, 2018, 09:50:20 am
I don't know if ~ is that easy to look up, check out variable types topic, it is the symbol for unsigned used to modify a signed type.
http://qb64.org/wiki/Variable_Types
Title: Re: Removing the tile bar/glitchy gui code
Post by: FellippeHeitor on August 03, 2018, 10:06:57 am
I really believe that

Quote
'~'

is a confused smiley.
Title: Re: Removing the tile bar/glitchy gui code
Post by: Fifi on August 15, 2018, 12:19:30 pm
Hi Fellippe,

Quote from: FellippeHeitor on August 02, 2018, 03:04:17 pm
Steve is right! And you can simplify that sample like this:

Code: QB64: [Select]
  1. '============
  2. 'NOBORDER.BAS
  3. '============
  4.  
  6.     FUNCTION GetWindowLongA& (BYVAL hwnd AS LONG, BYVAL nIndex AS LONG)
  7.     FUNCTION SetWindowLongA& (BYVAL hwnd AS LONG, BYVAL nIndex AS LONG, BYVAL dwNewLong AS LONG)
  8.     FUNCTION SetWindowPos& (BYVAL hwnd AS LONG, BYVAL hWndInsertAfter AS LONG, BYVAL x AS LONG, BYVAL y AS LONG, BYVAL cx AS LONG, BYVAL cy AS LONG, BYVAL wFlags AS LONG)
  10.  
  11. GWL_STYLE = -16
  12. WS_BORDER = &H800000
  13.  
  14. _TITLE "No Border"
  16.  
  17. PRINT "Press any key for no border...": A$ = INPUT$(1)
  18.  
  19. winstyle& = GetWindowLongA&(hwnd&, GWL_STYLE)
  20. a& = SetWindowLongA&(hwnd&, GWL_STYLE, winstyle& AND NOT WS_BORDER)
  21. a& = SetWindowPos&(hwnd&, 0, 0, 0, 0, 0, 39)
  22.  
  23. PRINT "Press any key to get back border...": SLEEP
  24.  
  25. winstyle& = GetWindowLongA&(hwnd&, GWL_STYLE)
  26. a& = SetWindowLongA&(hwnd&, GWL_STYLE, winstyle& OR WS_BORDER)
  27. a& = SetWindowPos&(hwnd&, 0, 0, 0, 0, 0, 39)
  28.  
  29. PRINT "The end"
  30.  
  31.  

I think such a check box option would be great in InForm to create windows without a frame border.

What do you think?

Best regards.
Title: Re: Removing the tile bar/glitchy gui code
Post by: FellippeHeitor on August 15, 2018, 12:20:44 pm
I'll take it into consideration, Fifi. Thanks!
Title: Re: Removing the tile bar/glitchy gui code
Post by: SMcNeill on September 16, 2018, 09:35:24 am
The biggest problem is GLUT doesn't play nice with all versions of Linux and borderless Windows.

http://openglut.sourceforge.net/group__window.html

Quote
GLUT_BORDERLESS seems to vary by the window manager on X11, though twm (for example) performs very similarly to WIN32. But KDE's window manager (for example) does not let you send keystrokes to borderless windows without OpenGLUT hacks.
Title: Re: Removing the tile bar/glitchy gui code
Post by: Omerta7486 on September 16, 2018, 12:54:38 pm
Quote
The world don't move to the beat of just one drum,
what might be right for you, may not be right for some.

Mm. Wise words Mr. Thicke!

The problem with an OS independent solution is that each OS handles window creation and functionality differently. For instance, Mac OSX uses GLUT, while Windows uses USER. Just look up documentation for both and compare the two. High level programming languages(Such as all forms of BASIC) are built to function generally under multiple environments; it's up to the programmer to pull in the OS specific functionality from OS native APIs. This means that you have to create OS specific versions of your app built around the different APIs. If you only wish to target a specific OS (https://store.steampowered.com/hwsurvey/Steam-Hardware-Software-Survey-Welcome-to-Steam), that would take a lot of pain out of the game. Hint: Over 95% of all Steam users are on PC(That's what I put a link to).

There's a reason developers often send their software off to a third party studio to be ported to a different OS. But, for us little guys, we usually pick an OS and stick with it.

By the by, Steve. If I may ask, can QB64 use different interpreters, or are the interpreters built in to the different versions(Win/Mac/Lin)? Not interested, just curious.
Text Only | Text with Attachments