AdvancedToolbarINIGuide for Opera 8.x/9.x
Here a try to unriddle the toolbar.ini a little bit, as an aid to `button creators`.
Note also similar docs for skin authors: AdvancedSkinGuide or SkinINIChanges and please note the CustomButtons page as well as the TTT-buttons page with more than 2000 Drag and drop buttons. Helpful also: AllActionsListPlus and AllActionsList (v9.x) as well as AllActionsList (v8.x)
Important addition:
About this guide:
The attention of this guide is turned to `how to create a button` and the syntax therefor. Take it as an aid to avoid most frequently failures.
- Create a sidebar with the complete table of contents for this guide. A link, clicked on the sidebar, opens the page in a normal main tab:
Create sidebar
Quick table of contents:
- Sections in the toolbar.ini
- General button syntax
...
- Precondition
- Buttontype
- Parameter pA, general button title
- Parameter pB, font size
- Parameter pC, specific skin section, test
- Parameter pD, button style, test
- Command
- Parameter p1, depends on the command/shortcut
- Parameter p2, depends on the command
- Parameter p3, command button title
- Parameter p4, button image name
...
- Operators
- More
Detailed table of contents:
Sections in the toolbar.ini [⊗]
Each toolbar is represented with one or several sections in the toolbar.ini, example:
[Search Panel Toolbar.alignment]
...
[Search Panel Toolbar.style]
...
[Search Panel Toolbar.content]
...
- Most important for buttons is the content-section, there you have to place your button entries; each button on a new line.
But here another interesting section entry concerning the Panels selector width:
[Hotlist Panel Selector.style]
Maximum Button Width=50
- This value sets the maximum width of the vertical Panel selector, in pixels. Works also for the bookmarks in the Personal bar [Personalbar.style], but not for the tabs with [Pagebar.style]; therefor you have to edit the skin.ini (see AdvancedSkinGuide-Options ).
(top)
General button syntax [⊗]
Please note first: on this button guide the four leading parameters in front of the `=`sign are hereinafter called: pA, pB, pC, pD as well as the other four parameters after the `=`sign are hereinafter called as: p1, p2, p3, p4
Button syntax:
Precondition,Buttontype,pA,pB,pC,pD=COMMAND,p1,p2,p3,p4
or detailed:
Precondition,Buttontype,General buttontitle-pA,Fontsize-pB,Skinsection-pC,Buttonstyle-pD=COMMAND,Depends-p1,Depends-p2,Command buttontitle-p3,Buttonimage-p4
- Only `Buttontype=Command` is really needed; parameters are mostly optional.
- Note, that the parameters pC and pD are for test purposes in Opera 9 only!
- Quotes; it is recommended to set the command with all it`s parameters and so on between quotes, but Opera does that for you the first time a toolbar section is changed (e.g. by drag and drop):
Precondition,Buttontype,pA,pB,pC,pD="Command,p1,p2,p3,p4"
- Note: Opera cannot detect the command if there is only one quote or a quote to much (a big source of error!)
- Note also: there are a lot of parameters which need to be between quotes too, please do not confuse them.
- Commas; if you need for example only the parameter pD (but not pA, pB and pC), you have to set the lacking commas as placeholder, example:
Buttontype,,,,pD=Command
- But also valid: commands or parameters never ends with a comma (otherwise Opera expects another parameter), correct example if you need only pA and p2:
Buttontype,pA=Command,,p2
There are more complex button structures if you are using the Operators mentioned later.
(top)
Precondition [⊗]
Optional. The Preconditions and combinations have to be in front of the buttontype! All the successional line content works only on that precondition.
Platform Unix,
Platform QNX,
Platform Mac,
Platform Windows,
Platform Win2000,
and combined platform preconditions found:
Platform Windows-Unix-QNX,
Platform Windows-Mac-QNX,
Platform Win2000-Unix-Mac,
Platform Windows-QNX,
Platform Unix-QNX,
Feature Voice,
Feature Feeds,
Feature Mail,
Feature Chat,
Feature MDI,
and combined feature preconditions found:
Feature Mail-Chat,
- Combined platform/feature preconditions found:
Platform Win2000-Unix-Mac, Feature Voice,
I think each combination is allowed, but not each may be useful.
(top)
Buttontype [⊗]
Sets the buttontype. The numbering of the buttons is recommended, please use always numbers which does not exists in the same section - in case of similar or equal buttons/commands it may be that a button not appears or not works as expected if Opera cannot differ via numeration (must not be consecutive but distinctive)!
Button12=
Quickbutton99=
Checkbox14=
Radiobutton15=
Dropdown16=
Multisearch177=
Quickfind18=
Edit19=
Account2=
Zoom23=
Address66=
Status24=
Identify25=
- Button a common button for several purposes
- Quickbutton works as long as the button is pushed, see More-Quickbutton
- Checkbox a checkbox for On/Off, see More-Checkbox
- Radiobutton a radiobutton for On/Off, see More-Radiobutton
- Dropdown a dropdownbox to choose something, see More-Dropdown
- Multisearch the searchbox with dropdown which let you choose something
- Quickfind the quickfindfield
- Edit the editfield
- Account the accountdropdownbox
- Zoom the zoomdropdownbox
- Address the addressfield with dropdown which let you choose something
- Status the statusfield available in Appearance - Buttons - Status or inside the Status bar (see also below `Status,x`)
- Identify the identify as `text-button`
Buttontypes with a parameter:
For the following buttontypes, the next (and only) parameter defines the `sort`:
Search,x a searchfield, the next parameter says which searchfield you wish:
Search16,x
Searchbutton,x a searchbutton, the next parameter says which search you wish:
Searchbutton30,x
Spacer,x a spacer, the next parameter says which spacer you wish:
Spacer21,x
- Spacer or Spacer,0 (fixed)
- Spacer,1 (dynamic)
- Spacer,3 (Wrapper)
Status,x displays the corresponding status text defined with a number as parameter after the comma:
Status231,x
- In use for the [Chat Room Header Toolbar.content] and [Chat Private Header Toolbar.content]: Status,1 is the tab/room name and Status,2 are the chat details.
- In use also for the [Mail Header Toolbar.content]: Status,2 are the mail details (x unread, x total), but also Status,1 is possible there - displaying the tab/mail name (Received, Outbox, Sent...).
- Interesting: Status,1 on any other toolbar, displays the title and the current tabs name you see also on the application bar at the top of Opera (Opera:config / Opera6.ini - User Prefs - Title).
- Status,2 on any other toolbar, displays the appropriate details to the open mail- or chat-tab; the details disappears if no such tab is open.
Progress,x displays the corresponding progressbar part defined through the parameter after the comma:
Progress22,x
- Progress or Progress,0 (document)
- Progress,1 (images)
- Progress,2 (total)
- Progress,3 (speed)
- Progress,4 (elapsed)
- Progress,5 (progress status)
- Progress,6 (progress simple)
- Progress,7 (clock, yes the clock is part of the progressbar...)
(top)
Parameter pA, general button title [⊗]
Optional, sets the general button title you wish (between quotes; "WOW thats my button"), or sets the general button title taken from the language file (language file code without quotes!), examples:
- Displays `WOW thats my button` as title:
Button28,"WOW thats my button"=
- Displays the general title in the chosen language. Matching title codes you find in the language file (.lng):
Button14,0123456789=
- If the button title is not defined here, you have to define it with the 3rd parameter after the `=`sign (p3) for each command, otherwise no title appears. If you define the title twice (pA and p3), normally the p3-title would be taken.
- In case of using the operators `|` or `>` the pA button title may be used as general title instead of individual titles for each command.
- Since Opera 9 all entries in the language file (.lng) are numbered in a new way; with nine- or ten-digit numbers now. After some primarily difficulties it seems to be this way now:
- Toolbar.ini and Menu.ini for Opera 9.x only: please use the new numbers only.
- Toolbar.ini and Menu.ini for Opera 8.x AND 9.x: please use the old numbers, but in case of items which exists in Opera 9.x only use the new numbers. Opera seems to `translate` the old numbers into the new numbering if you change a toolbar (e.g. by drag and drop). We all hope this `translating mechanism` will stay as it is; otherwise there is a lot of work for all the button- and menu-tweakers...
(top)
Parameter pB, font size [⊗]
Optional, sets the fontsize for the button title (default if not defined is: 100):
Button1050,pA,110=
(top)
Parameter pC, specific skin section [⊗]
Optional, since Opera 9 for test purposes, sets a specific skin.ini section you wish as button image:
Button122,pA,pB,3=
- Nothing, 0 or 1 is the `Push button skin` with the `Push default button skin` for .pressed, .selected and so on
- 2 is the original button image normally defined in `Images`
- 3 is `Selector button skin`
- 4 is `Link button skin`
- 5 is `Tab button skin`
- 6 is `Pagebar button skin`
- 7 is `Header button skin`
- 8 is `Menu button skin`
- 9 is the `Push button skin` again, but here with it`s own sections for .pressed, .selected and so on
- 10 is `Radio button skin`
- 11 is `Checkbox skin`
It seems the above skin.ini sections are in use with all the subsections if available, e.g. .hover, .selected, .pressed and so on.
The images are drawn around the button title if you are using: 1, 2, 5, 6, 7, 8, 9. The `Link button skin` (4) seems only to display the text.
- Hold in mind: the third and fourth parameter in front of the `=`sign you can only use for test purposes: they are changed automatically by Opera 9.x into normal buttons, checkboxes and radio buttons without 3./4. parameter as soon as the toolbar is changed, e.g. you drag and drop something on the concerned toolbar!
(top)
Parameter pD, button style [⊗]
Optional, since Opera 9 for test purposes, sets the button style you wish for the buttons you set with pC:
Button87,pA,pB,pC,2=
- 0 is `Images only`
- 1 is `Text only`
- 2 is `Image with text below`
- 3 is `Image with text on right`
- `Image with text below` (2) seems only to work for the specific skin image pC 2, the normal button image.
- Interesting: in case you set pC to `2` (normal button image) you are able to set the button style with pD different to the general settings for a toolbar. That allows for instance a button set to `Image with text on right` between buttons set to `Image with text below` through the option in Customize - Toolbars - Style, or a button with title between buttons without titles...
- Hold in mind: the third and fourth parameter in front of the `=`sign you can only use for test purposes: they are changed automatically by Opera 9.x into normal buttons, checkboxes and radio buttons without 3./4. parameter as soon as the toolbar is changed, e.g. you drag and drop something on the concerned toolbar!
(top)
Examples pA-pD
Correct examples for the things in front of the `=`sign:
Button100=
Button100,pA=
Button100,pA,pB=
Button100,pA,pB,pC=
Button100,pA,pB,pC,pD=
Platform Windows-Unix-QNX,Button100,pA,pB,pC,pD=
Feature voice,Button100,pA,pB,pC,pD=
Platform Unix-QNX,Feature Mail-Chat,Button100,pA,pB,pC,pD=
And some varieties:
Button100,,pB,,pD=
Button100,pA,,pC,pD=
Button100,pA,pB,,pD=
Button100,,pB,pC,pD=
Button100,,,,pD=
Button100,,pB=
Button100,,pB,pC=
Button100,pA,,pC=
and so on...
(top)
Command [⊗]
The command says what you wish to do with the button. Each button must have at least one valid command. You find such commands inside the mouse-, toolbar-, menu- and keyboard-ini, as well as in `Opera:config` and here in the Operawiki: AllActionsList.
Button13=Back
Button14=Forward
Button27=Rewind
- It is recommended to set the command with all it`s parameters and so on between quotes, but Opera does that for you the first time a toolbar section is changed (e.g. by drag and drop):
Button10="Command,p1,p2,p3,p4"
- Note: Opera cannot detect the command correctly if there is only one quote, a quote on the wrong place or a quote to much (a big source of error!)
- Note also: if a button contains a wrong or inexistent command, Opera sets automatically `External action,` in front of the command (in case of changing a toolbar by drag and drop). That means: the command is not recognized and with the `External action`-addition the command will never work.
- There are more complex button structures if you are using the Operators mentioned later.
The following examples are commands for multiple purposes; the first parameter p1 defines their sense (see the examples for p1 below):
Button14=Manage,...
Button19=Focus panel,...
Button56=Show popup menu,...
Button59=Show hidden popup menu,...
Button80=Show preferences,...
Button87=Set preference,...
(top)
Parameter p1, depends on the command/shortcut [⊗]
Optional, depends on the command, examples with commands for multiple purposes:
- Opens the `Notes tab`, there are more things for `Manage`, see also Manage:
Button17=Manage,"Notes"
- Opens the `Search panel`, valid: Search, Bookmarks, Mail, Contacts, Chat, Notes, Transfers, History, Links, Windows, Info, Music (and Widgets since Opera 9):
Button27=Focus panel,"Search"
- Opens the `Bookmarks menu` and displays the dropdown arrow at the right (valid is each section name from the menu.ini):
Button37=Show popup menu,"Browser bookmarks menu"
- Opens the `Bookmarks menu` (hides the dropdown arrow; you have to hold the button for a while for the menu):
Button37=Show hidden popup menu,"Browser bookmarks menu"
- Opens the `Preferences dialog` with the `Advanced` tab on top (see the Preferences list):
Button27=Show preferences,4
- Activates the `Tooltips`. `Set preference` with the next parameter is only available in Opera 9; `User prefs` and `Popup Button Help` represents the corresponding section and entry in Opera:config (see also the complete list):
Button47=Set preference,"User prefs|Popup Button Help=1"
- Hold in mind that for several commands available through `Set preference,...` it is necessary to restart Opera...
Parameter p1 for shortcuts in the title:
If a command includes a standard shortcut, you are able to display or hide the shortcut via p1. This concerns only the title appearing in the status bar/field and in the tooltips.
- No p1: this button displays `Go (Shift+Enter)` as title in the status bar/field and in the tooltips:
Button13,870715797=Go
or
Button13=Go,,,870715797
- With `1` as p1: this button displays only `Go` as title everywhere:
Button11,870715797=Go,1
or
Button11=Go,1,,870715797
If p1 is intended to be in use for other purposes, it can be that other values are recommended. For instance: the command `Show preferences` can have 0, 1, 2, 3, 4 as p1 for the `General, Wand, Search, Web pages or Advanced` tabs on top, so you must display/hide the shortcut in another way:
- No p1: this button displays only `Preferences` as title everywhere:
Button12,294279971=Show preferences
or
Button12=Show preferences,,,294279971
- With `-1` as p1: this button displays `Preferences (Ctrl+F12)` as title in the status bar/field and in the tooltips:
Button13,294279971=Show preferences,-1
or
Button13=Show preferences,-1,,294279971
- Note also: the appearing shortcuts are associated to the command and not to the title!
- And: what happens with shortcuts defined by yourself?
(top)
Parameter p2, depends on the command [⊗]
Optional, depends on the command, specifies normally the first parameter p1, examples:
Button1010=Command,p1,p2
- Open page in... . The `%u` as p2 delivers here the current address (document URL) to the program specified in p1 (see also More-Variables):
Button122=Execute program,"c:\programs\mozilla firefox\firefox.exe","%u"
- The `6` as p2 defines what happens with p1 (opens the hotlist/panels):
Button750=Set alignment,"hotlist",6
(top)
Parameter p3, command button title [⊗]
Optional, sets the individual command button title you wish (between quotes; "WOW thats my button"), or sets the command button title taken from the language file (language file code without quotes!), examples:
- Displays `WOW thats my button` as command title:
Button28=Command,,,"WOW thats my button"
- Displays the command title in the chosen language. You find the matching code in the language file (.lng):
Button14=Command,,,0123456789
- If the command button title is not defined here, you have to define it with the first parameter in front of the `=`sign (pA) as general button title, otherwise no title appears. If you define the title twice (pA and p3), normally the p3-title would be taken.
- If you have a button which uses `|` or `>` as operator, it is recommended to set a command button title for each individual command (there are restrictions, see: Operator `|` and Operator `>` ).
- Since Opera 9 all entries in the language file (.lng) are numbered in a new way; with nine- or ten-digit numbers now. After some primarily difficulties it seems to be this way now:
- Toolbar.ini and Menu.ini for Opera 9.x only: please use the new numbers only.
- Toolbar.ini and Menu.ini for Opera 8.x AND 9.x: please use the old numbers, but in case of items which exists in Opera 9.x only use the new numbers. Opera seems to `translate` the old numbers into the new numbering if you change a toolbar (e.g. by drag and drop). We all hope this `translating mechanism` will stay as it is; otherwise there is a lot of work for all the button- and menu-tweakers...
(top)
Parameter p4, button image name [⊗]
Optional, sets the buttons image you wish; the name here (between quotes) has to correspond with an image name in the skin.ini (normally an entry in the section [Images] there, the skin.ini associates the image name with the corresponding .png-file), examples:
Button103=Command,p1,p2,p3,"Button image name"
or
Button103=Command,,,,"Button image name"
- Displays the image for `Back`/`Forward` defined inside the section [Images] in the skin.ini:
Button123=Command,,,,"Back"
or
Button125=Command,,,,"Forward"
- Important: for common commands it is not necessary to set p4; Opera takes the image associated through the command. But it is necessary with all commands for multiple purposes (e.g. Manage, Focus panel, Show popup menu, and so on) or if you like to have another than the standard image, as well as for buttons with the operators `|` and `>` which may provide individual command button images.
- Each skin.ini section works, but hold in mind, that it is not possible to draw images around the button title.
(top)
Examples p1-p4
Correct examples for the things behind the `=`sign:
Button100=command
Button100=Command,p1
Button100=Command,p1,p2
Button100=Command,p1,p2,p3
Button100=Command,p1,p2,p3,p4
And some varieties:
Button100=Command,,,,p4
Button100=Command,,,p3,p4
Button100=Command,,,p3
Button100=Command,,p2
Button100=Command,p1,,,p4
Button100=Command,,p2,,p4
and so on...
(top)
Operators [⊗]
There are four complemental operators which allows complex buttons:
- The operator ` + ` allows a second function like a menu on the dropdown arrow at the right, or each other command as second function for `hold the button for a while` without dropdown arrow.
- The operator `&` allows to include more commands, they are recognized together with the main command
- The operator ` | ` allows two commands, usually for On/Off-buttons
- The operator ` > ` allows multiple commands, with enhanced possibilities for changing titles and images
(top)
The operator ` + `, arrow/hold [⊗]
Allows a second function like a menu with a dropdown arrow at the right, but allows also each other command as second function (then normally you have to hold the button for a while, but there are some tricks...).
Related also: Show popup menu as command displays the dropdown arrow, but Show hidden popup menu hides the arrow. You can call each section title from the menu.ini as popup menu.
Here some examples with dropdown arrow:
- Only menu; this button displays a menu as only function (and the dropdown arrow at the right, title: `Style`, image: `Back`):
Button131=Show popup menu,"Style menu",,"Style","Back"
- Function+Menu; this button opens a new page as main function and displays a menu by clicking the dropdown arrow at the right (title: `New`, image: `Back`):
Button132=New page,,,67499,"Back" + Show popup menu,"Style menu"
- Menu+Menu; this button displays a menu as main function and displays another menu by clicking the dropdown arrow at the right (title: `Bookms`, image: `Back`):
Button133=Show popup menu,"Browser bookmarks menu",,"Bookms","Back" + Show popup menu,"Style menu"
- Menu+Function; tricky, this button displays a menu as main function and opens a new page by clicking the dropdown arrow at the right (title: `Bookms`, image: `Back`):
Button134=Show hidden popup menu,"Browser bookmarks menu",,"Bookms","Back" + New page & Show popup menu,"-"
- The above button is not intended by Opera (no menu no=dropdown arrow), but ` & Show popup menu,"-"` at the end refers to a not existing menu ("-") and makes the arrow available.
- Function+Function; tricky, this button reloads the current page as main function and opens a new page by clicking the dropdown arrow at the right (title: `Re-load`, image: `Back`):
Button135=Reload,,,"Re-load","Back" + New page & Show popup menu,"-"
- Also the above button is not intended by Opera (no menu=no dropdown arrow), but also here; ` & Show popup menu,"-"` at the end refers to a not existing menu ("-") and makes the arrow available.
And here the examples but without dropdown arrow:
- Only Menu; this button displays a menu as only function (without dropdown arrow, title: `Style`, image: `Back`):
Button140=Show hidden popup menu,"Style menu",,"Style","Back"
- Function+Menu; this button opens a new page as main function and displays a menu if you hold the button for a while (without dropdown arrow, title: `New`, image: `Back`):
Button141=New page,,,67499,"Back" + Show hidden popup menu,"Style menu"
- Menu+Menu; this button displays a menu as main function and displays another menu if you hold the button for a while (without dropdown arrow, title: `Bookms`, image: `Back`):
Button142=Show hidden popup menu,"Browser bookmarks menu",,"Bookms","Back" + Show hidden popup menu,"Style menu"
- Menu+Function; this button displays a menu as main function and opens a new page if you hold the button for a while (without dropdown arrow, title: `Bookms`, image: `Back`):
Button143=Show hidden popup menu,"Browser bookmarks menu",,"Bookms","Back" + New page
- Function+Function; this button reloads the current page as main function and opens a new page if you hold the button for a while (without dropdown arrow,title: `Re-load`, image: `Back`):
Button144=Reload,,,"Re-load","Back" + New page
Something special:
The above button `Only Menu` without dropdown, works correct, but if you accidentally hold the button a while - nothing happens. To avoid that you can set the command twice:
- Only Menu special; this button displays a menu as only function and works also if you hold the button a while (without dropdown arrow, title: `Style`, image: `Back`):
Button145=Show hidden popup menu,"Style menu",,"Style","Back" + Show hidden popup menu,"Style menu"
Another special:
In the Panel header toolbar you find a text-button which displays the current panels title and shows the `panel menu`. This button you can have also for any other toolbar:
Button200,69682=Show popup menu,"Internal panels" + Show hidden popup menu,"Internal panels"
- In this case only `Show hidden...` works not (hides the whole text), so you must set the command twice, with the advantage of a hidden dropdown arrow which is not necessary here. It is also needed to set a button title in pA (69682 is the language file code for `Panels`), because if set in p3, the title disappears if no panel is open.
And...:
I think all the things are to complicated to explain, but with the above examples you are able to create each imaginable button with this operator.
- IMPORTANT: all `hold-buttons` with a function after the `+` (not a menu/hidden menu) works only properly if you have activated the `Special effects` in Tools - Appearance - Skin (since Opera 9)!
- Hold in mind, that after the `+`sign the parameters p3 and p4 are ignored; it is not possible to display a separate title or image for a second menu/function after the `+`.
- Note also: if you are using the other operators for a button with more than one command, you cannot assign a menu or a second function to a individual command; a menu/second function is always assigned to the whole button. So it is recommended to set the `+` with a menu/second function always at the end, after all other commands and parameters!
(top)
The operator `&` [⊗]
Allows to include more commands which are recognized together with the main command:
Button200=Command1,p1,p2,p3,p4 & Command2,p1,p2
or
Button200=Command1,p1,p2,p3,p4 & Command2,p1,p2 & Command3,p1,p2 (and so on)
- After the `&`sign the parameters p3 and p4 are ignored; it is not possible to display a separate title or image for additional commands after the `&`.
- You cannot be sure that the commands are recognized in sequence, take as a rule: always recognized together!
- If you have a button with several commands throuh the operators `|` or `>` which indicates the status with images and you inserts more commands with `&` to switch them together, the images cannot indicate the status correctly: as long as one of the several commands is `true` the image is displayed (or vice versa)!
(top)
The operator ` | ` [⊗]
Allows two commands, e.g. On/Off buttons with two commands. Recognized by Opera is always the command which is `not true`.
- Changing button titles with p3 possible if that is provided by Opera for the involved commands, otherwise changing titles are not possible.
- Also changing button images with p4 possible if that is provided by Opera for the involved commands. If this is not the case: changing images are only available via skin.ini and `.selected`, `.pressed`, `.open` and so on, also valid if you use parameter pC for a general image (pC since Opera 9 available).
- Normally in use for buttons with two commands; but with more commands recommended for the button type Dropdown.
- Provided commands; this button displays the titles `Stop` or `Reload` taken from the language file and the images for Stop and Reload from the skin.ini:
Button140, 21235=Stop | Reload,,,21210
or
Button140=Stop,,,21235 | Reload,,,21210
or
Button140="Stop,,,21235,"Stop" | Reload,,,21210,"Reload""
- Commands not provided; this button displays only the title `Enable Gif` and the image for `Enable GIF animation` or `Enable GIF animation.selected` from the skin.ini (if these images are defined there):
Button120,"Enable Gif"="Enable GIF animation | Disable GIF animation"
or
Button120="Enable GIF animation,,,"Enable Gif" | Disable GIF animation"
- In case of not provided commands the pA button title is in use as general title, but also p3 on the first command works as general title.
There is no list which commands are provided or not; you have it to try out.
(top)
The operator ` > ` [⊗]
Allows multiple commands, with different titles and images. Recognized by Opera is always the next command after the command which is currently `true` - after the last command follows the first. The first command is recognized too in case of no command is currently `true` or if several commands are currently `true`.
- You must define a command button title with p3 for each individual command (otherwise no title appears). If the title is defined with the parameter pA the `general` title stays for each command the same.
- Here you must also define a button image with p4 for each individual command (otherwise no image appears). Since Opera 9 you can use also parameter pC for a general image.
- In general: normally no changing images are available via skin.ini and `.selected`, `.pressed`, `.open` and so on.
- I`m not sure but I think also here the involved commands must be provided for this purpose in order to have different titles/images?
- This button displays four different titles and four different images (if they are defined in the skin.ini):
Button480="Disable popup windows,,,52201 > Enable popup windows,,,52200 > Enable popup windows in background,,,52202 > Enable requested popup windows,,,67424"
(top)
Table of contents:
(top)
Button type, Checkbox and Radiobutton [⊗]
The button type Checkbox= you can use for On/Off `buttons`.
- This checkbox toggles the gif animation On/Off:
Checkbox333=Enable gif animation,,,"Gif" | disable gif animation
- There is no difference between | and > as operator; only one title available and the image is given.
Also a Radiobutton= as button type you can use for On/Off `buttons`, with the same effect as the checkbox above.
- This radiobutton toggles the gif animation On/Off:
Radiobutton334=Enable gif animation,,,"Gif" | disable gif animation
- There is no difference between | and > as operator; only one title available and the image is given.
- Hold in mind, that such a checkbox or radiobutton displays it`s title always, even if you set the toolbar to `Images only`!
- In some cases it may be necessary to use the images for a checkbox or radiobutton as parameter p4 (e.g. title hidden if `Images only`). Here the specific image names from the skin.ini: `Checkbox skin` and `Checkbox skin.selected`, `Radio button skin` and `Radio button skin.selected`.
(more)
(top)
Button type, Dropdown [⊗]
A Dropdown= as button type displays a dropdownbox in order to choose between several commands.
- This Dropdown lets you choose between five browsers, using title-code taken from the language file:
Dropdown650=Identify as,0,,52210 | Identify as,1,,52211 | Identify as,2,,52212 | Identify as,3,,52213 | Identify as,4,,52214
- Please use always the operator ` | ` for dropdowns.
- Menus, called from inside a dropdown-box: works not properly!
(more)
(top)
Button type, Quickbutton [⊗]
The button type Quickbutton= executes the command as long as the button is pushed. In Opera only used for a voice button. But there are also other imaginable purposes.
- This quickbutton displays the handheld mode as long as pushed (with the image for `Back`):
QuickButton602=Enable handheld mode,,,67406,"Back" | Disable handheld mode
- Similar buttons are imaginable for instance with `Zoom` or `Fit to width`. Such buttons and much more you find on the TTT-Buttons page
(more)
(top)
Command, Manage [⊗]
Syntax:
Button632=Manage,"..."
Manage, "panel tabs":
Valid as p1 after `Manage,` are: Search, Bookmarks, Mail, Contacts, Chat, Notes, Transfers, History, Links, Windows, Info, Music (and Widgets since Opera 9),
Manage, "nothing":
Because each button needs a valid command, it is sometimes necessary to have a valid Command without effect.
- This button displays a visible spacer (if the image is defined in the skin.in) without title, but if you click the button it happens - nothing:
Button995,=Manage,"-",,,"Spacer image"
- `Manage,` is a valid command in order to call a tab, but it refers to the inexistent tab `"-"`, effect: nothing happens.
- This button displays a comment, to us for instance in `My buttons` or anywhere:
Button996,"COMMENT-TEXT"=Manage,"-"
Manage other things:
There are a lot of commands with `Manage` but without comma, e.g. `Manage wand` or `Manage contacts`. See the AllActionsList.
(more)
(top)
Command, Save with images [⊗]
In Opera 8.x we had the commands `Save document` or `Save document as` in order to save without images and `Save document with images as` in order to save with images (stored in the same folder). New in Opera 9: `Save document with images as` is no longer valid, but `Save document as,1` saves with images (the images stored in a separate folder!). I tried to combine the commands for the use in Opera 8.x AND 9.x, but because 8.x knows both (`Save document as` and `Save document with images as`) such a button works not properly; displays the dialog twice (8.x) or hides the button image due to unknown command (9.x). But here a tricky solution:
- This button works in Opera 8.x as well as in Opera 9.x: click the button to save the document without images, but click the dropdown arrow to save with images (8.x - images in the same folder, 9.x - images in separate folder):
Button280="Save document,1,,21205 + Save document with images as | Save document as,1 + Show popup menu,"-""
- Also the next button works in Opera 8.x as well as in Opera 9.x: click the button to save the document without images, but hold the button for a while in order to save with images (8.x - images in the same folder, 9.x - images in separate folder):
Button290="Save document,1,,21205 + Save document with images as | Save document as,1"
- Please note: for both of the above buttons the shortcut you see normally together with the title in the tooltips or in the status bar/field is hidden via p1 for the main command.
- Note also: Opera 9.x writes automatically `External action` in front of the unknown command `Save document with images as` if you change something on the toolbar by drag and drop. That means: this command is not recognized, Opera jumps to the next valid command and the button works still as expected.
(more)
(top)
Parameter, Variables [⊗]
In some cases you need one of the variables below as parameter (normally for p2 or p3):
- "%c" (clipboard content)
- "%l" (address of a link you right-click)
- "%s" (filename of local source cache)
- "%t" (currently selected text)
- "%u" (current document url)
- Mainly the variable "%u" is in use as p2 for Open page in... . Some other examples you find on: IniFileVariables
- The variable "%l" normally only to use for a link related context menu inside the menu.ini.
(more)
(top)
Parameter, Preferences list [⊗]
Only for Opera 9; with the command and the next parameter Show preferences,x it is possible to open the `Preferences dialog` with the desired tab and category on top (see also: Parameter p1)
Here the complete tabs list:
- Show preferences,-1 (General tab or last used tab, with shortcut `(Shift+F12)` in statusbar/field and tooltips - title, but all the following without shortcut there)
- Show preferences (General tab or last used tab)
- Show preferences,0 (General tab or last used tab)
- Show preferences,1 (Wand tab)
- Show preferences,2 (Search tab)
- Show preferences,3 (Web pages tab)
- Show preferences,4 (Advanced tab)
And here the complete Advanced tabs categories list:
- Show preferences,10 (Category `Tabs` or last used category)
- Show preferences,11 (Category `Tabs`)
- Show preferences,12 (Category `Browsing`)
- Show preferences,13 (Category `Notifications`)
- Show preferences,14 (Category `Content`)
- Show preferences,15 (-NOTHING, prepared for Java-)
- Show preferences,16 (-NOTHING, prepared for Plug-Ins-)
- Show preferences,17 (Category `Fonts`)
- Show preferences,18 (Category `Downloads`)
- Show preferences,19 (Category `Programs`)
- Show preferences,20 (Category `History`)
- Show preferences,21 (Category `Cookies`)
- Show preferences,22 (Category `Security`)
- Show preferences,23 (Category `Network`)
- Show preferences,24 (Category `Toolbars`)
- Show preferences,25 (-NOTHING, prepared for Menus-)
- Show preferences,26 (Category `Shortcuts`)
- Show preferences,27 (-NOTHING, prepared for Mouse-)
- Show preferences,28 (Category `Voice`)
(more)
(top)
Special effects must be activated for second function [⊗]
- IMPORTANT since Opera 9: all buttons with a function after the `+`sign (not a menu/hidden menu) works only properly if you have activated the `Special effects` in Tools - Appearance - Skin (since Opera 9)! Not easy to understand, but true... (thanks to Goop and Stoen)
(more)
(top)
Here you find a lot of Drag and drop buttons: CustomButtons and TTT-buttons
bbc persian main page
173.244.181.42 (2011-04-03 14:56:28)