I'm running v2.09.3 as Kiosk mode.
First, I was wondering if the Alt+F4 combination key can be disabled from the browser? If not, it's no big deal since PWB can restart by itself!
Second, can the scrollbars be hidden, at least the horizontal one? I know Opera's kiosk mode can do this and it works really well.
Thanks!
Disable Alt+F4 and scrollbars?
Moderators: Tyler, Scott, PWB v2 Moderator
You can disable the Alt-F4 by disabling exiting PWB.
[Browser]
DisableExit=True
However it has been proven using Internet Explorer over a long period of time on poorly written web pages can cause memory leaks.
http://msdn.microsoft.com/library/defau ... tterns.asp
For this reason we usually recommend allowing PWB to exit. Because PWB is solely dependant on Internet Explorer for all its web browsing capabilities, it is possible that the underlying Internet Explorer is leaking memory because one or more pages it is displaying is not closing something correctly, and this is causing PWB problems. These types of problems may not have an affect in the short term, but over time can cause all types of problems. To avoid memory leak problems you should have PWB, and thus Internet Explorer, restart at least once a day.
The best way to run PWB in my opinion is to use the inactivity timer set to exit, the restart on close set to true, and allow patrons to close the browser when they are finished. This used in conjunction with the clear cache on close allows PWB to clean up the Internet Explorer cache files, and restart the underlying Internet Explorer to clean up any memory problems. Plus this technique gives the next patron a "fresh" browser to work with that does not have any links clicked, no cookies set, and no history to worry about.
To do this effectively, you need to take PWB out of Kiosk mode, enable the close button, allow exiting, and start PWB and HideGUI form the registry. This is described in the following post.
http://www.teamsoftwaresolutions.com/ph ... .php?t=536
When the computer is logged onto PWB, and HideGUI are started. HideGUI hides all the windows elements, and PWB browses to the home page. When a patron is finished they close PWB and PWB restarts itself. If the patron walks away the inactivity time causes PWB to exit and PWB restarts itself. Because HideGUI does not allow any of the Windows GUI to show there is no danger of the patron gaining access to Windows. In either case PWB cleans up Internet Explorer and gives the next patron a fresh browser.
--Scott
[Browser]
DisableExit=True
However it has been proven using Internet Explorer over a long period of time on poorly written web pages can cause memory leaks.
http://msdn.microsoft.com/library/defau ... tterns.asp
For this reason we usually recommend allowing PWB to exit. Because PWB is solely dependant on Internet Explorer for all its web browsing capabilities, it is possible that the underlying Internet Explorer is leaking memory because one or more pages it is displaying is not closing something correctly, and this is causing PWB problems. These types of problems may not have an affect in the short term, but over time can cause all types of problems. To avoid memory leak problems you should have PWB, and thus Internet Explorer, restart at least once a day.
The best way to run PWB in my opinion is to use the inactivity timer set to exit, the restart on close set to true, and allow patrons to close the browser when they are finished. This used in conjunction with the clear cache on close allows PWB to clean up the Internet Explorer cache files, and restart the underlying Internet Explorer to clean up any memory problems. Plus this technique gives the next patron a "fresh" browser to work with that does not have any links clicked, no cookies set, and no history to worry about.
To do this effectively, you need to take PWB out of Kiosk mode, enable the close button, allow exiting, and start PWB and HideGUI form the registry. This is described in the following post.
http://www.teamsoftwaresolutions.com/ph ... .php?t=536
When the computer is logged onto PWB, and HideGUI are started. HideGUI hides all the windows elements, and PWB browses to the home page. When a patron is finished they close PWB and PWB restarts itself. If the patron walks away the inactivity time causes PWB to exit and PWB restarts itself. Because HideGUI does not allow any of the Windows GUI to show there is no danger of the patron gaining access to Windows. In either case PWB cleans up Internet Explorer and gives the next patron a fresh browser.
--Scott
That is actually a great idea! That is, the part to close on inactivity and restart itself to give a fresh browser for the new user. Thanks! I did notice that the DisableExit is there but it's a pain when you do need to close it for x-reason. I wasn't aware of the memory leaks so your suggesting will work well.
This HideGUI, does it just hide Windows GUI, like start menu and so forth? If so, I've completely taken care of that using a Group Policy.
As for the scrollbar, this is what I mean. Check out the pictures. PWB's shows the scrollbar while the Opera kiosk mode doesn't. I'm not really sure why or if it can be disabled.
PWB thumbnail below:
Opera thumbnail below:
This HideGUI, does it just hide Windows GUI, like start menu and so forth? If so, I've completely taken care of that using a Group Policy.
As for the scrollbar, this is what I mean. Check out the pictures. PWB's shows the scrollbar while the Opera kiosk mode doesn't. I'm not really sure why or if it can be disabled.
PWB thumbnail below:
Opera thumbnail below:
HideGUI can do the following things.
[GUI]
HideDesktop=True
HideTaskbar=False
HideStartButton=False
HideTaskTray=False
HideTaskbarButtons=False
CloseTaskTray=False
CloseStartButton=False
[Keys]
DisableEnable=False
DisableWindowsKey=True
DisableApplicationsKey=True
DisableCtrlEsc=True
DisableShiftEnter=True
DisableTaskSwitching=True
DisableAltSpace=True
DisableCtrlKey=False
DisableAltKey=False
[Mouse]
DisableEnable=False
DisableRightClick=False
DisableShiftLeftClick=False
But if you can acheive what you need with group policies then I would use them.
Normally in kiosk mode you would disable the scrollbars via code in the home page, and allow other pages to display as the designer intended.
<body scroll="no">
Currently PWB can not disable the scrollbars for all pages, but it should not be a problem to add into our next release of PWB.
--Scott
[GUI]
HideDesktop=True
HideTaskbar=False
HideStartButton=False
HideTaskTray=False
HideTaskbarButtons=False
CloseTaskTray=False
CloseStartButton=False
[Keys]
DisableEnable=False
DisableWindowsKey=True
DisableApplicationsKey=True
DisableCtrlEsc=True
DisableShiftEnter=True
DisableTaskSwitching=True
DisableAltSpace=True
DisableCtrlKey=False
DisableAltKey=False
[Mouse]
DisableEnable=False
DisableRightClick=False
DisableShiftLeftClick=False
But if you can acheive what you need with group policies then I would use them.
Normally in kiosk mode you would disable the scrollbars via code in the home page, and allow other pages to display as the designer intended.
<body scroll="no">
Currently PWB can not disable the scrollbars for all pages, but it should not be a problem to add into our next release of PWB.
--Scott
Disabling the scrollbars was an easy addition. Although this version will probably not be released because PWB v2.10 is on the way, you can benefit from the added functionality now by downloading the following file, copying the new EXE over the old EXE, and adding the following to your INI file.
http://www.team2s.com/new/PWBv2094.zip
[Browser]
...
DisableScrollBars=True
...
Disabling the scrollbars only affects the main window.
--Scott
http://www.team2s.com/new/PWBv2094.zip
[Browser]
...
DisableScrollBars=True
...
Disabling the scrollbars only affects the main window.
--Scott