// This is the "positioning from page anchors" code used by the advanced positioning expressions.
page.elmPos = function(e, p) {
	var x = 0, y = 0, w = p ? p : this.win;
	e = e ? (e.substr ? (isNS4 ? w.document.anchors[e] : getRef(e, w)) : e) : p;
	if (isNS4) {
		if (e && (e != p)) {
			x = e.x;
			y = e.y;
		}
		if (p) {
			x += p.pageX;
			y += p.pageY;
		}
	} else if (e && e.focus && e.href && this.MS && /Mac/.test(navigator.platform)) {
		e.onfocus = new Function('with(event) {self.tmpX = clientX - offsetX;' + 'self.tmpY = clientY - offsetY}');
		e.focus();
		x = tmpX;
		y = tmpY;
		e.blur();
	} else {
		while(e) {
			x += e.offsetLeft;
			y += e.offsetTop;
			e = e.offsetParent
		}
	}
	return{x:x, y:y};
};

// Add animation to the 'pMenu' menu object for supported browsers.
// Opera doesn't support clipping so we turn it off, and Mozilla versions prior to
// 1.x (such as Netscape 6) are too slow to support it, so disable there too.
// If you don't want animation, delete this entirely, and the menus will act normally.
// Change the speed if you want... it's the last number, between -100 and 100, and is
// defined as the percentage the animation moves each frame.
// The 'menuAnim' function is in the "Optional Code" section below, edit if you want to,
// I've put in a few extra tweaks in there like fading transitions if you're interested.
if (!isOp && navigator.userAgent.indexOf('rv:0.')==-1) {
	pMenu.showMenu = new Function('mN','menuAnim(this, mN, 10)');
	pMenu.hideMenu = new Function('mN','menuAnim(this, mN, -10)');
	// Alternatively: try the IE5.5+/Windows filters. Comment above two lines out and uncomment:
	//pMenu.showMenu = function(mN)
	// { menuFilterShow(this, mN, 'progid:DXImageTransform.Microsoft.fade(duration=1)') }
	// There's a good list of transitions available from http://msdn.microsoft.com
	// Add animation to other menu objects like this...
	//anotherMenu.showMenu = new Function('mN','menuAnim(this, mN, 10)');
	//anotherMenu.hideMenu = new Function('mN','menuAnim(this, mN, -10)');
}
// Advanced (or just plain determined to tweak everything) users: Custom item arrangement!
// Here you can extend a menu's overall dimensions, and then reposition or resize its items.
// You can arrange the items however you want within a menu, in a curve or similar,
// or even change the overall arrangement of the menu (put items in rows etc).
// Individual items have .iX and .iY which are positions and .iW and .iH which are dimensions.
// I recommend doing this *before* calling the border or shadow commands too :).
//with (pMenu.menu)
//{
// mFile[0].menuW += 20;
// mFile[0].menuH += 20;
// mFile[1].iX += 5;
// mFile[2].iX += 2;
// mFile[2].iW -= 2;
// mFile[3].iX += 5;
// mFile[4].iX += 10;
// mFile[4].iW += 10;
// mFile[4].iY += 3;
//}
// *** (4) EVENTS ***
//
// In JavaScript, there are document 'events' you need to set so any scripts you are using
// are notified of things like page loading/clicking/scrolling. If you've got several menus
// or another JavaScript entirely in your page, you'll need to add all their functions in here.
// For another menu object, call its functions like update() and position() next to pMenu's,
// I've put examples in to show where these need to go.
//    The reason for these is that every time you set them, they override a previous setting.
// So make sure you collate all the functions that need to be called in here! Syntax:
//object.onevent = function()
//{
// function1();
// function2();
// ...
//}
// That's similar to: <BODY ONEVENT="function1(); function2(); ...">
// The most important event is one used to display the menu by calling one of several methods of
// any menu object(s) you have created. This is where you select the menu creation mode. 'Dynamic'
// mode inserts the menus into the document once it has finished loading and supports features
// like modifying the menu after creation. You update a menu in 'Dynamic' mode by just calling the
// .update() method of a menu object like 'pMenu'.
//    'Fast' creation mode writes the menus to the document here and now, which is faster and
// more reliable in many browsers but only when the document's loading -- you do this by passing
// 'true' without quotes to the update function to signal that we're inline.
//    Opera only supports Fast mode and Netscape 4 only supports in Dynamic mode, so we use
// browser-detect code here. If you find some browser has troubles with one mode or another, try
// the other menu creation method -- see the "Cross-Browser" code at the very top of the SCRIPT
// tag for the variables used.
//    Hardcore tweakers -- there's some extra code commented in the popOver() function at the top
// which lets you create the root menu on page load and other menus only as needed, which might
// be useful for very very large menus in a single frame. Look it up if you want.
if (!isNS4) {
	// Write menus now in non-NS4 browsers, by calling the "Fast" mode .update(true) method.
	pMenu.update(true);
	//anotherMenu.update(true);
} else {
	// For Netscape 4, back up the old onload function and make a new one to update our menus.
	// This is the regular "Dynamic" mode menu update, it works in IE and NS6 too if required.
	var popOldOL = window.onload;
	window.onload = function() {
		if (popOldOL) popOldOL();
		pMenu.update();
		//anotherMenu.update();
	}
}
// Other events must be assigned, these are less complicated, just add or remove menu objects.
var nsWinW = window.innerWidth, nsWinH = window.innerHeight, popOldOR = window.onresize;
window.onresize = function() {
	if (popOldOR) popOldOR();
	if (isNS4 && (nsWinW!=innerWidth || nsWinH!=innerHeight)) history.go(0);
	pMenu.position();
	//anotherMenu.position();
}
window.onscroll = function() {
	pMenu.position();
	//anotherMenu.position();
}
window.onload = function() {
	pMenu.position();
	//anotherMenu.position();
}
// NS4 can't reliably capture clicks on layers, so here's a workaround.
if (isNS4) {
	document.captureEvents(Event.CLICK);
	document.onclick = function(evt) {
		with (pMenu) if (overI) click(overM, overI);
		//with (anotherMenu) if (overI) click(overM, overI);
		return document.routeEvent(evt);
	}
}
// Activate the window.onscroll() event in non-Microsoft browsers.
if (!isIE || isOp) {
	var nsPX = pageXOffset, nsPY = pageYOffset;
	setInterval('if (nsPX! = pageXOffset || nsPY! = pageYOffset) ' + '{ nsPX = pageXOffset; nsPY = pageYOffset; window.onscroll() }', 50);
}
// *** (5) OPTIONAL CODE ***   DELETE IF YOU'RE NOT USING THESE!
// MOUSE EVENTS:
//
// If you want, you can assign functions to handle mouse events like mouse over/out/click.
// You'll want to use these for assigning click actions to 'sm:' items or status messages etc.
// 'with (this)' means use the properties of the menu object, and it's passed the current
// menu name (mN) and item number (iN) you can use to calculate the active item.
// To uncomment and activate, delete the /* and */ at the start and end.
/*
pMenu.onclick = function(mN, iN) {
	with (this) {
		// Do actions depending on the item that the mouse was over at the time of the click.
		// You may with to use nested IFs or 'switch' statements etc. if you're familiar with JS.
		if (mN == 'root') {
			if (iN == 1) status = 'Congratulations, you\'ve mastered clicking!';
			// Click on second item in root menu will navigate to 'edit.html'. Copy and paste this for
			// each menu item to add click actions to 'sm:' items...
			if (iN == 2) location.href = 'edit.html';
			if (iN == 3) location.href = 'help.html';
		}
	}
}
// Set the status message to the URL if the 'action type' is nothing, and clear on mouseout.
pMenu.onmouseover = function(mN, iN) {
	with (this) {
		// By now, you either have my JS Object Browser script from my site or you need it... try
		// embedding in an IFrame and typing 'pMenu' into its Go To field to see the menu internals.
		with (menu[mN][iN]) if (!type) status = href;
	}
}
pMenu.onmouseout = function() { status = '' }
*/
// ANIMATION:
//
// Each menu object you create by default shows and hides its menus instantaneously.
// However you can override this behaviour with custom show/hide animation routines,
// as we have done in the "Menu Effects" section. Feel free to edit this, or delete
// this entire function if you're not using it. Basically, make functions to handle
// menuObj.showMenu() and .hideMenu(), both of which are passed menu names.
//
// Customisers: My lyr.clip() command gets passed the parameters (x1, y1, x2, y2)
// so you might want to adjust the direction etc. Oh, and I'm adding 2 to the dimensions
// to be safe due to different box models in some browsers.
// Another idea: add some if/thens to test for specific menu names...?
function menuAnim(menuObj, menuName, dir) {
	// The array index of the named menu (e.g. 'mFile') in the menu object (e.g. 'pMenu').
	var mD = menuObj.menu[menuName][0];
	// Add timer and counter variables to the menu data structure, we'll need them.
	if (!mD.timer) {
		mD.timer = 0;
	}
	if (!mD.counter) {
		mD.counter = 0;
	}
	with (mD) {
		// Stop any existing animation.
		clearTimeout(timer);
		// If the layer doesn't exist (cross-frame navigation) quit.
		if (!lyr || !lyr.ref) {
			return;
		}
		// Show the menu if that's what we're doing.
		if (dir > 0) {
			lyr.vis('visible');
		}
		// Also raise showing layers above hiding ones.
		lyr.sty.zIndex = 1001 + dir;
		// Alpha fade in IE5.5+. Mozilla's opacity isn't well suited to this as it's an inheritable
		// property rather than a block-level filter, and it's slow, but uncomment and try it perhaps.
		// WARNING: This looks funny if you're mixing opaque and translucent items e.g. solid menus
		// with dropshadows. If you're going to use it, make sure all your alpha values for a given
		// menus are numbers, or they're all null (solid).
		//if (isIE && window.createPopup) lyr.alpha(counter&&(counter<100) ? counter : null);
		// Clip the visible area. Tweak this if you want to change direction/acceleration etc.
		lyr.clip(0, 0, menuW+2, (menuH+2)*Math.pow(Math.sin(Math.PI*counter/200),0.75) );
		// Remove clipping in NS6 on completion, seems to help old versions.
		if ((isDOM && !isIE) && (counter >= 100)) {
			lyr.sty.clip = '';
		}
		// Increment the counter and if it hasn't reached the end (10 steps either way),
		// set the timer to call the show/hide function again in 40ms.
		counter += dir;
		if (counter > 100) {
			counter = 100;
		} else if (counter < 0) {
			counter = 0;
			lyr.vis('hidden');
		} else {
			timer = setTimeout(menuObj.myName + '.' + (dir > 0 ? 'show' : 'hide') + 'Menu("' + menuName + '")', 40);
		}
	}
}

// Here's the alternative IE5.5+ filter animation function.
function menuFilterShow(menuObj, menuName, filterName) {
	var mD = menuObj.menu[menuName][0];
	with (mD.lyr) {
		sty.filter = filterName;
		var f = ref.filters;
		if (f && f.length && f[0]) {
			f[0].Apply();
		}
		vis('visible');
		if (f && f.length && f[0]) {
			f[0].Play();
		}
	}
}

// Extra code for updating and moving the menus is embedded in the feature list in the HTML document
// below, have a look at that if you're interested in tweaking the menu more.
// *** (6) FRAMESET README ***
// You're looking at the single-frame version of this script right now. This menu does support
// frames with a few extensions -- the core script is the same, but you need to remove the "Events"
// section and include a modified version of it in each loaded file. Get the frameset example from
// my site first, I've put the modified section in a file named "SUBFR.JS".
//
// This script should reside in the topmost frameset. Files loaded in this frameset must satisfy
// two conditions to work:
// 
// 1) They must have all the needed CSS info from the <STYLE> tag included in them, and a small
// JavaScript file (SUBFR.JS) to activate and manage the menus in that frame.
// 
// 2) They must be from the same domain as this frameset -- you can't load in search results or
// similar from another server and pop menus out over it, due to browser JS security rules.
// 
// With the SUBFR.JS file, all you have to do is make sure that in the first line pMenu points to
// the correct pMenu -- that is, located within that frame's parent (this script). If you're using
// multiple menu objects across frames or loading framesets within framesets, you will have to edit
// it, otherwise just leave it as is. To use multiple menus, you need to create them both here and
// then edit SUBFR.JS in the same fashion as the Events section here, calling your second menu
// object whenever pMenu itself is called.
// 
// The example setup allows the menus in sub-frames scroll with their windows. All you have to do is
// use the 'page' object in that frame in a formula to get the current scrolling position of that
// frame, and then add or subtract pixels to position the menus from the scroll position, e.g. for a
// menu in a frame named 'xyz', we would set it to appear in that frame and appear near the top and
// 100px from the left:
// 
// startMenu('menuName', false, 'xyz.page.scrollX()+100', 'xyz.page.scrollY()+10', 17, hBar, 'xyz');
// 
// Of course, third-level menus in other frames can be positioned relative to their parents
// normally. (Remember: strings as positions mean 'absolute' and are calculated as formulae,
// numbers as positions mean 'relative', offset from its parent).
// 
// JS window syntax is OK, so parents can be 'xyz.subFrame.something' if you want, and the SUBFR
// file in that frame/window points back to this one (try scrWin=top rather than scrWin=parent).
// You'll probably want to specify target frames for each menu item, in the same fashion as
// you specified them for the menus themselves -- by default URLs will open in the window in
// which the script is located, the topmost frameset. Try addItem('Text', 'file.html', 'botFr');
