We had Privacy Buttons setup in K-M 1.53 but cannot find how to put them in K-M 1.54.

Can someone please explain step by step how to get the following buttons on the toolbar:

COOKIES, IMAGES, JAVASCRIPT, POPUPS, CACHE, CLEAR COOKIES, CLEAR ALL, KILL FLASH, USER AGENT.

(Please note that the titles of the buttons above are typed in caps for ease of readability and are not done so for shouting.)

Thanks for any help. (Love K-M, btw.)

If you mean that you need To active The Privacy Bar .

In The Main Toolbar:

View >> Toolbars >> Privacy Bar. (Click on it)

Or do You mean that you have problem in the Privacy Bar?

OK. Found it and turned it on, but it is only showing CACHE, COOKIES, PASSWORDS (only shown in CLEARING mode, not in the TOGGLE ON/OFF mode).

How do we get the other functions (listed in original post) to be added and accessible in the Privacy Bar?

This is for K-M 1.54.

--Is this something we have to edit in the about:config, in order to get the other BUTTONS showing on Privacy Bar? We want to be able to turn on/off Cookies, Javascript, etc. (as noted in original post) without having to drill down into menus to access those buttons.

Hope this is clear and thanks for your help.

Just edit toolbars.cfg located in skins\[the skin you're using], and uncomment the buttons you need.

A+

---

Mozilla/5.0 (x11; U; Linux x86_64; fr-FR; rv:38.0) Gecko/20100101 Ubuntu/12.04 K-Meleon/76.0

---

Web: http://jujuland.pagesperso-orange.fr/
Mail : alain [dot] aupeix [at] wanadoo [dot] fr

---

Ubuntu 12.04 - Gramps 3.4.9 - Harbour 3.2.0 - Hwgui 2.20-3 - K-Meleon 76.0 rc

---

Edited 1 time(s). Last edit at 12/21/2012 08:12AM by JujuLand.

you need to edit toolbars.cfg in the current skin folder.

Get into this file and find section looking like

%ifplugin macros|privacy

&Privacy Bar(54,10){

	%ifplugin macros

	Cookies{
	macros(pref_ToggleCookies)
	Block Cookies
	privbar_red.bmp[0]
	privbar_green.bmp[0]
	}

	Images{
	macros(pref_ToggleImages)
	Block Images. Press F9 to toggle.
	privbar_red.bmp[1]
	privbar_green.bmp[1]
	}

	Java{
	macros(pref_ToggleJava)
	Block Java Applets
	privbar_red.bmp[2]
	privbar_green.bmp[2]
	}

	JavaScript{
	macros(pref_ToggleJavaScript)
	Block JavaScript. Press F7 to toggle.
	privbar_red.bmp[3]
	privbar_green.bmp[3]
	}

	Popups{
	macros(pref_TogglePopups)
	Block Popups. Press F8 to toggle.
	privbar_red.bmp[4]
	privbar_green.bmp[4]
	}

	Referer{
	macros(pref_ToggleReferer)
	Block HTTP Referer
	privbar_red.bmp[5]
	privbar_green.bmp[5]
	}

	%endif
	
#	%ifplugin privacy

#	Clear Cache{
#	privacy(ClearCache)
#	Clear Cache
#	privbar_red.bmp[6]
#	privbar_green.bmp[6]
#	}

#	Clear Cookies{
#	privacy(ClearCookies)
#	Clear Cookies
#	privbar_red.bmp[7]
#	privbar_green.bmp[7]
#	}

#	Clear History{
#	privacy(ClearHistory)
#	Clear History
#	privbar_red.bmp[8]
#	privbar_green.bmp[8]
#	}

#	Clear Passwords{
#	privacy(ClearSignon)
#	Clear Passwords
#	privbar_red.bmp[9]
#	privbar_green.bmp[9]
#	}

#	Clear URLBar{
#	privacy(ClearMRU)
#	Clear URL Bar History
#	privbar_red.bmp[10]
#	privbar_green.bmp[10]
#	}

#	%endif
	
	%ifplugin macros
	
      Kill Applets{
	macros(JS_killApplets)
	Kill Java Applets
	privbar_red.bmp[13]
	privbar_green.bmp[13]
	}

      Kill Flash{
	macros(JS_killFlash)
	Kill Flash Objects
	privbar_red.bmp[12]
	privbar_green.bmp[12]
	}

	%ifplugin macros & privacy
	Clear All{
	macros(kPrivacy_ClearAll)
	Clear All
	privbar_red.bmp[11]
	privbar_green.bmp[11]
	}

	%endif
	-
	User Agent{
	ID_APP_ABOUT|&User Agent
	Check Browser Identity. Right-click to choose different User Agent.
	privbar_red.bmp[14]
	privbar_green.bmp[14]
	}

	%endif

}

%endif

The code may be slightly different as it may refer to button images named other way.

Every such a piece

	Popups{
	macros(pref_TogglePopups)
	Block Popups. Press F8 to toggle.
	privbar_red.bmp[4]
	privbar_green.bmp[4]
	}

represents 1 button on toolbar

All lines starting with # - are commented (non-active).
In my example all 'clear something' buttons are commented - thus they are hidden from toolbar. You have vice versa situation, I understood.
Uncomment them deleting # signs and you'll get the needed buttons.

Or just get into same file from your old 1.5.3 and copy all the section from there.



Edited 2 time(s). Last edit at 12/21/2012 08:15AM by rodocop.

Quote
Beleaguered
OK. Found it and turned it on, but it is only showing CACHE, COOKIES, PASSWORDS (only shown in CLEARING mode, not in the TOGGLE ON/OFF mode).

How do we get the other functions (listed in original post) to be added and accessible in the Privacy Bar?

This is for K-M 1.54.

--Is this something we have to edit in the about:config, in order to get the other BUTTONS showing on Privacy Bar? We want to be able to turn on/off Cookies, Javascript, etc. (as noted in original post) without having to drill down into menus to access those buttons.

Hope this is clear and thanks for your help.

That clear now , as JujuLand and rodocop said you have simple problem in skin folder due Toolbars organize by install new Skin (in this case by the developer) .

which Not Effect on the Privacy Bar functions which locate in main.kmm macros.

So simply open toolbars.cfg by text editor (like Notepad ) and delete the "#" from :

# ButtonName(width,height){
# .
# It's properties
# .
# }

If the Button name block not there , you can copy it from your old KM Skin And paste it inside the Privacy Bar :

%ifplugin macros|privacy
&Privacy Bar(64,13){
.
Buttons Blocks
.
.
.
}

And change its images (.bmp) to the new one.

then save the file restart KM.

-------------------

Another method :

If you Like you old KM skin.

Open your Old KM , go to about:config , type skinsCurrent , will display your current skin .

open old KM skin folder and copy the current skin folder .

Then go to you New KM skin folder , paste the old skin , If there folder by the same name , don't overwrite , but paste it in another place else, Rename it (something like Old skin) .

Then drag it to New KM skin folder .

Go to preference [F2] >> GUI Appearance >> Skin >> ( Chose your Old skin ).

I played a bit with buttons awhile ago, and found K-Meleon is a little unusual in the way it handles button management.
First thing to understand is that the *selection* of buttons and the *look* of buttons are NOT independent here.
If you switch to another skin, then not only the looks are switching, but also the selection of buttons, there can be a lot more or a lot less, depending on the choice of the original skin author. Because in K-Meleon each individual skin folder contains not only the button images (.bmp) but also an individual selection file (.cfg).
A few special buttons (bookmark buttons etc.) are additionally created by plugins or macros, NOT this cfg-file.

Now there are several ways possible to adjust those buttons individually, whatever one likes best:

* View / Toolbars (works instantly)

or
* View / Toolbars / Options...

or
* Edit / Configuration / Toolbars
This opens directly the config file in the currently chosen skin.
Each button consists of a few lines to point it to an image and define its actions on left- or right-click.
Add or remove the comment signs # on a button block to hide or show a button.
--> changes appear after next browser start
--> you need writing rights in that folder!

or
* Use your file manager and edit/copy/paste whatever you like, images, button definitions, their left-click commands and their right-click-menus, create all new buttons or copy stuff from one skin to another etc. Total freedom there.
For example you could copy on old customized cfg-file from Klassic-skin in KM1.5.3 to the Klassic folder in KM1.5.4
Or copy over single skin folders from an older KM-version to a newer one, which may need adjusting a button or two if a command name was changed (look it up in the default skin of the newer version)
The skin folders are located in the program folder, usually something like
c:/programs/K-Meleon/skins/name1
c:/programs/K-Meleon/skins/name2
...
You can even create a folder ...skins/default and put in there special images that ALL skins can use.
You can even create a folder ...skins/name1(large) or ....skins/Klassic(test) or whatever, put an own cfg-file in it and only a few changed images, and those skin variations will catch the missing images from their family-folder (the one without () in the name).

If I recall correctly it was also possible to create skin folders in the current profile folder, there are usually less probs with writing rights, but not sure anymore.

A little?!
KM is absolutely unusual thing about skinning!

JamesD is working now on advanced Skin Switcher for easy changing themes without UI 'destruction'.

But we cannot synchronize themes in terms of button images ordering without adopting the standard of button numbering in skin image files.

That is the next task on the KM-way to future.