[Xerte] Controlling Nav buttons

[Dave Burnett]

All very useful, but why is something that shows up in debug as the correct value not be evaluated by the statement?

I tried to use the sequence you described:

currentFW.nextPage() and currentFW.prevPage()

As you pass into various sub FWs, in their entry frames do currentFW = whatever this FW is;
How does mine differ:

cur_fw_id = icon.parentNode.parentNode.attributes.id; // in SCR in FW_ENT

//In previous button
debug(cur_fw_id); //shows correct id of i65777
cur_fw_id.prevPage(); //does nothing

If I put the actual value in:
165777.prevPage(); //works fine




Subject: RE: [Xerte] Controlling Nav buttons
Date: Fri, 20 Nov 2009 22:21:41 +0000
From: Julian.Tenney at nottingham.ac.uk
To: xerte at lists.nottingham.ac.uk










icon //is an XMLNode
icon.parentNode;//is its parent XMLNode
icon.parentNode.clip() //gives you the movieclip instantiated from that node;
 
clip() is a method that all XMLNodes get - here are some other useful ones like findChildByName(), findParentByID() - see the help.



From: xerte-bounces at lists.nottingham.ac.uk on behalf of Dave Burnett
Sent: Fri 20/11/2009 19:14
To: Xerte list
Subject: RE: [Xerte] Controlling Nav buttons



Is there a trick I'm missing to pass the curr fw id variable  into statements:

cur_fw_id = icon.parentNode.parentNode.attributes.id;
debug(cur_fw_id); //shoes correct id
cur_fw_id.prevPage(); //does nothing

If I put the actual value in:
165777.prevPage(); //works fine








Subject: RE: [Xerte] Controlling Nav buttons
Date: Fri, 20 Nov 2009 16:17:08 +0000
From: Julian.Tenney at nottingham.ac.uk
To: xerte at lists.nottingham.ac.uk







You can use duplicates as longa s they aren’t on the stage together, so in different apges, yes you can.
 
Here’s what I like to do:
 
Add the back and next buttons in the main entry frame. In the scripts do
 
currentFW.nextPage() and currentFW.prevPage()
 
As you pass into various sub FWs, in their entry frames do currentFW = whatever this FW is;
 
Then you have one set of controls that can navigate lots of FWs.
 
 


From: xerte-bounces at lists.nottingham.ac.uk [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Dave Burnett
Sent: Friday, November 20, 2009 4:10 PM
To: Xerte list
Subject: RE: [Xerte] Controlling Nav buttons
 
Thanks Julian, I'll check out that handler for the implications.
If I give multiple RES items the same rs, does that set up a conflict, or will they all be affected the same? 





Subject: RE: [Xerte] Controlling Nav buttons
Date: Fri, 20 Nov 2009 15:40:25 +0000
From: Julian.Tenney at nottingham.ac.uk
To: xerte at lists.nottingham.ac.uk

In an onOpenPage event handler?
 
Or even in the button scripts…
 


From: xerte-bounces at lists.nottingham.ac.uk [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Dave Burnett
Sent: Friday, November 20, 2009 3:26 PM
To: Xerte list
Subject: [Xerte] Controlling Nav buttons
 

Now I have a handle on global navigation, on to local navigation.

I can see a few ways to do this, but is there a best practice for hiding/showing Next and Previous buttons in a classic page turner setup?

Giving the buttons in question an rs value and using the Visible property looks like the way to go, but where's the best place for the controlling code?

Cheers,

Dave 




Windows 7: It works the way you want. Learn more.
 



Hotmail: Trusted email with powerful SPAM protection. Sign up now.


Windows 7: I wanted simpler, now it's simpler. I'm a rock star.  		 	   		  
_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141665/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.nottingham.ac.uk/pipermail/xerte/attachments/20091120/9e8ca68a/attachment.html