1) How do you reduce the size of the buttons on the toolbar?
2) I turned on the chevrons for the toolbar but noticed no difference in appearance? What does this feature do?
3) If I restrict a site in the url.txt file such as '-yahoo.com' do I have to also restrict the IP address in the ip.txt file? Or altenatively, if I allow access to a site in the url.txt file do I also have to allow access in the ip.txt file?
TIA,
Dan
PWB v2.04 Questions
Moderators: Tyler, Scott, PWB v2 Moderator
1. The buttons on the toolbar are fixed in size. We do have plans to make them variable in a future release of PWB. The buttons on the shell bar are determined by the title of the shortcut used for the button and are sized to the longest named shortcut. To reduce the size of the shell bar buttons, reduce the length of the shortcut with the longest name.
2. The chevrons, when enabled will show on the right side of the toolbar when the length of the toolbar is longer then what is shown. When the chevron is clicked on a drop down list will be displayed containing the buttons that are not currently visable.
3. The URL and IP filters work indendantly. PWB first checks the URL filter then the IP filter. If the URL filter denies access the IP filter will not have a turn to to check the IP as the browse will have been canceled.
--Scott
2. The chevrons, when enabled will show on the right side of the toolbar when the length of the toolbar is longer then what is shown. When the chevron is clicked on a drop down list will be displayed containing the buttons that are not currently visable.
3. The URL and IP filters work indendantly. PWB first checks the URL filter then the IP filter. If the URL filter denies access the IP filter will not have a turn to to check the IP as the browse will have been canceled.
--Scott
New version of PWB
Currently running PWB 2.4. Now there is v2.4r1 available. What do I have to do to upgrade the current version.
RE: new version PWB
Thanks for your response...
One more question...What are the advantages /disadvantages of just copying the EXE over the old EXE without touching the INI file. Is what you wrote below all there is to it?
Your response
If you are already running PWB v2.04, download the upgrade and copy the EXE over the old EXE. The INI file was not changed between revisions.
One more question...What are the advantages /disadvantages of just copying the EXE over the old EXE without touching the INI file. Is what you wrote below all there is to it?
Your response
If you are already running PWB v2.04, download the upgrade and copy the EXE over the old EXE. The INI file was not changed between revisions.
In order to just copy the EXE over the old EXE when changing versions, for example v2.03 to v2.04, you will need to disable the INI file checking in the INI file.
If you are upgrading from v2.04 revision x to another revision, the INI file was not changed so you will benefit from the bug fixes and you do not have to worry about configuration changes.
If you disable the INI file checking and upgrade to v2.04 from v2.xx, PWB will use the internal default values when a key is not found in the INI file. This may or may not fit your needs.
--Scott
If you are upgrading from v2.04 revision x to another revision, the INI file was not changed so you will benefit from the bug fixes and you do not have to worry about configuration changes.
If you disable the INI file checking and upgrade to v2.04 from v2.xx, PWB will use the internal default values when a key is not found in the INI file. This may or may not fit your needs.
--Scott