Page Title: Object Menu PRO v2 – Manual – BobsCreations

  • This webpage makes use of the TITLE meta tag - this is good for search engine optimization.

Page Description:

  • This webpage DOES NOT make use of the DESCRIPTION meta tag - this is NOT GOOD for search engine optimization.

Page Keywords:

  • This webpage DOES NOT make use of the KEYWORDS meta tag - whilst search engines nowadays do not put too much emphasis on this meta tag including them in your website does no harm.

Page Text: “settings:click_menu = on”, You only change the data after the =. Make sure not to remove the “, at the end of the line as this will break the script. Main Menu The main menu is the menu you get when you click the object. “menu:main:menu = button1, button2, button3”, Your menu may consist of up to 12 buttons. Inside your main menu you may also want to include the CLOSE button as defined by settings:close_button. “menu:main:menu = button1, button2, CLOSE, button3, button4, Light”, For a button to do something you need to define a action or sub menu: “menu:main:Light = something”, This is a action. When the Light button is clicked “something” is done. “menu:Light:menu = button1 ,button2”, This is a sub menu. When the light button is clicked it gives a sub menu with button1 and button2. (Note: a BACK button is automatically included in all sub menus. The sub menu can contain up to 11 buttons) “menu:Light:button1 = something”, This is a action for the sub menu for when button1 is clicked. Integers The integer options holds a on or off value that you can use inside of your blue dialog menu and there values can be changed by menu buttons. If you for example would create a lamp: “integer:light = off”, When we rez the lamp the light is off. So we set the integer to Off, which is the default. This setting will automatically create the [light] tag that we can use in our menu text. “menu:light:menu = On, Off”, “menu:light:text = Light: [light]”, Create a sub menu with a On and Off button and the light status in the menu text. “menu:light:on = light | -4 | 1 | <0.8, 0.4, 0.0> | 1.0 | 5.0 | 1.0”, “menu:light:on = integer | on”, Set the light to on and change the integer to on. “menu:light:off = light | -4 | 0 | <0.8, 0.4, 0.0> | 1.0 | 5.0 | 1.0”, “menu:light:off = integer | off”, Set the light to off and change the integer to off. Prim numbers & names All menu buttons that let you specify a prim supports either a prim number or prim name. It is recommended that you use a prim name or negative link number when possible (so when you re-link your item you don’t need to change the numbers). menu:color:red = color | 2 | <1.000, 0.255, 0.212> | -1 Change the prim with link number 2 to red. menu:color:red = color | a1 | <1.000, 0.255, 0.212> | -1 Change the prim with the name a1 to red. Negative link numbers are also supported: -1 = All prims. -3 = All children (all except root). -4 = The prim the script is in. For faces you can either use the face number or -1 for all faces. Examples There are multiple examples included with the Object Menu PRO. You want to rez and edit these examples to see how they work. They make it a lot easier to understand. Here is the example of a simple lamp (the “light prim” is named a1): “integer:main = off”, “menu:main:On = glow | a1 | -1 | 0.1”, “menu:main:On = light | a1 | 1 | <0.8, 0.4, 0.0> | 1.0 | 5.0 | 1.0”, “menu:main:On = integer | on”, “menu:main:Off = glow | a1 | -1 | 0.0”, “menu:main:Off = light | a1 | 0 | <0.8, 0.4, 0.0> | 1.0 | 5.0 | 1.0”, “menu:main:Off = integer | off” Menu buttons As previously explained a “main menu button” can either do something or open a sub menu. Bellow a list of the button options with examples: Access Set who can access the menu. Format: access | owner/group/everyone “menu:main:menu = Button1, Button2, CLOSE, Access“, “menu:Access:menu = Owner, Group, Everyone”,

  • This webpage has 571 words which is between the recommended minimum of 250 words and the recommended maximum of 2500 words - GOOD WORK.

Header tags:

  • It appears that you are using header tags - this is a GOOD thing!

Spelling errors:

  • This webpage has 3 words which may be misspelt.

Possibly mis-spelt word: button1

Suggestion: button
Suggestion: buttons
Suggestion: button 1

Possibly mis-spelt word: button2

Suggestion: button
Suggestion: buttons
Suggestion: button 2

Possibly mis-spelt word: button3

Suggestion: button
Suggestion: buttons
Suggestion: button 3

Broken links:

  • This webpage has no broken links that we can detect - GOOD WORK.

Broken image links:

  • This webpage has no broken image links that we can detect - GOOD WORK.

CSS over tables for layout?:

  • It appears that this page uses DIVs for layout this is a GOOD thing!

Last modified date:

  • We were unable to detect what date this page was last modified

Images that are being re-sized:

  • This webpage has no images that are being re-sized by the browser - GOOD WORK.

Images that are being re-sized:

  • This webpage has no images that are missing their width and height - GOOD WORK.

Mobile friendly:

  • After testing this webpage it appears to be mobile friendly - this is a GOOD thing!

Links with no anchor text:

  • This webpage has no links that are missing anchor text - GOOD WORK.

W3C Validation:

Print friendly?:

  • It appears that the webpage does NOT use CSS stylesheets to provide print functionality - this is a BAD thing.

GZIP Compression enabled?:

  • It appears that the serrver does NOT have GZIP Compression enabled - this is a NOT a good thing!