frame : contentFrame

Generated List Scroller - HTML version
The HTML-version of the GLS comes with 5 standard jump-buttons (jumpX=1 to jumpX=5), keep these reserved for categories or divisions in the menu.. add or take them out to your liking
test jump 1 (link1, content.htm, targetframe= default)
test jump 11 (link12, page2.htm, targetframe= default)
test jump 10 (link11, page1htm, targetframe= default)
test jump 6 (link6, page1.htm, targetframe= 'iframe')
test jump 8 (link8, page3.htm, targetframe= 'contentbottom1')
test jump 9 (link9, page1.htm, targetframe= 'contentbottom2')
test jump 18 (link10, test.htm, targetframe= default)
see list .txt file

Automaticly update GLS-html menu with html-links in non-menu frames:

In the html-GLS model you can optionaly use the jumpX values/variables from the list .txt file (which were initialy developed to create the option for shortcut-buttons to categories in the list) to use html links within your html-pages which are in non-menu frames and at the same time update the menu (active/position etc) Try out the example links above, you'll see that not only does it open the link (defined in the list .txt value), but also updates the position, highilighted/active menu-item and current selected item-text in the GLS menu.

This is done with an extra JavaScript, so beware that not 100% of all browsers/platforms will support it. The jump.js file contains the script which sends a variable to the GLS menu (.swf file) in the menu frame and tells it to perform 2 call functions (these 2 call functions will actualy open the correct link and update the menu). So in reality the html-link is blank, the flash menu is the component which actualy opens the page. Of course you can use normal html-links but it won't update the menu.

The jump.js file reads

function send_jump(nr)
	{
  	top.leftFrame.document.menu.SetVariable("gls:jump",nr);
  	top.leftFrame.document.menu.TCallFrame("gls/jumper", 1);
  	top.leftFrame.document.menu.TCallFrame("gls/jumper", 2);
	}

Whenever you change the 'tree-level' of the loaded GLS, you will need to adjust the jump.js accordingly. (default GLS is loaded in MC instance "gls"). If you for example create a Movie Clip inside Movie Clip 'gls' and give it instance name 'test', and you decide to load the GLS into the movieclip 'test' instead of directly in 'gls', then you'll need to correct the jump.js file to

top.leftFrame.document.menu.SetVariable("gls/test:jump",nr);
top.leftFrame.document.menu.TCallFrame("gls/test/jumper", 1);
top.leftFrame.document.menu.TCallFrame("gls/test/jumper", 2);

Remember that you may start with jumpX with X the same number as the value of linkX, as soon as you insert more links/lines inside the list.txt the X value of link and jump will start varying more and more. In the list .txt fily you can see for example; it started out with linkX and jumpX-variable same values when having 17 menu-items. when I inserted a line at link10 (using the Listmanager which does not come with trial version) it required a jump value of 18 ( &jump10=18) since 1 to 17 were already taken. jump10 received value 18... this is unavoidable but does not give any actual problems for the GLS.