[RESOLVED] Issue with fullscreen code

[Jenner]

If this is something that is designed to run "kiosk mode", he can change all the window settings design-time. I've written a number of programs designed to be full-screen dominant, hiding the fact that there's even an operating system running underneath, or an easy way to access it. For things like shop-floor control systems, message-boards being displayed on large, airport style displays, and kiosks, this is just an everyday thing. passel pretty much nailed everything that needs to be done for the basics. Disabling, or making it hard to access the underlying operating system is trickier.

[jdc20181]

He doesn't want to maximize the form, he wants to make it "fullscreen", i.e. the client area fills the full screen, no window decorations.



Me.FormBorderStyle = Windows.Forms.FormBorderStyle.None
Me.Size = SystemInformation.PrimaryMonitorSize
Me.Location = New Point(0, 0)
Me.TopMost = True

Since you are processing things in an event handler for a control that you are manipulating, that might be an issue, I don't know.
I would try to do the control manipulation outside the control's event handler.
So, put the code into a sub, and then invoke the sub asynchronously to see if that helps.
For instance, create a sub named makeFullScreen and put the code in there.
In the event handler asynchronously Invoke the sub by using BeginInvoke:

Me.BeginInvoke( makeFullScreen)

That way your code will have left the event handler for the toolstrip before trying to hide the toolstrip.
Since the toolstrip would want to draw the button pressed in the up state when you release the button, but you've also told it to hide itself

Yep that is the goal - to make it "Fullscreen" by doing what I did it hides the task bar (But the issue is it doesn't do it the first time around)

Ah I see. Well, you can still use maximized and border style none.

However...

Changing the border style of a form can cause funky things to happen, in VS2005 it was terrible, and caused events to loose their handlers. In 2010, it's better but can cause some errors (I can easily generate stack overflow errors when changing a form border style).

I believe changing the style causes the window handle to be recreated (thinking back to the C++ days), but could be wrong.

The code hides the task bar because there is no Me.GoFullScreen() Function - So The code is different than what you have been describing.

If this is something that is designed to run "kiosk mode", he can change all the window settings design-time. I've written a number of programs designed to be full-screen dominant, hiding the fact that there's even an operating system running underneath, or an easy way to access it. For things like shop-floor control systems, message-boards being displayed on large, airport style displays, and kiosks, this is just an everyday thing. passel pretty much nailed everything that needs to be done for the basics. Disabling, or making it hard to access the underlying operating system is trickier.

Kisok mode? I have no clue what that is - The project is my browser project. It is a function that all major browsers have.




If y'all wanna see what it does you can always download it and try it yourself : http://beffsbrowser.tk

The screenshots made the demo - so you don't need to download but - if you wish ^ there is teh website - Currently in version 1.6.0

Thanks.


I am gonna try The suggestion passel said.

And seeing what the reduced code does.

However -


The code should make the taskbar disappear. With the taskbar it isn't fullscreen.


Thanks again.