[Xerte] Controlling Nav buttons

[Dave Burnett]

and then a minute passed...

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



















A penny drops…

 





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:26 PM

To: Xerte list

Subject: RE: [Xerte] Controlling Nav buttons





 

The
fog is slowly lifting.

So no code effect if it is not on the stage.

But if I mess with the underlying nodes I could pre-set it.   







Subject:
RE: [Xerte] Controlling Nav buttons

Date: Fri, 20 Nov 2009 16:17:46 +0000

From: Julian.Tenney at nottingham.ac.uk

To: xerte at lists.nottingham.ac.uk



You’d be back to page one of
the FW, with the interaction rebuilt, so it would behave as it did the first
time.

 





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:14 PM

To: Xerte list

Subject: RE: [Xerte] Controlling Nav buttons





 

The
script approach was the first I considered, but then I wondered what happened
if the user activated that script, then navigated away from that FW.

Would the button be visible on return to the FW (because the interaction would
be rebuilt)?











Subject:
RE: [Xerte] Controlling Nav buttons

Date: Fri, 20 Nov 2009 16:05:50 +0000

From: Julian.Tenney at nottingham.ac.uk

To: xerte at lists.nottingham.ac.uk



So in your button script do
this

//next button

 

If (fw.currentPage <
fw.pageCount – 1){

  //navigate

} else {

  btnNext._visible =
false;//or whatever

}

 





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:03 PM

To: Xerte list

Subject: RE: [Xerte] Controlling Nav buttons





 

Thanks
Paul.  I may need to structure some of the stuff that way.



In this case I have regular pages of content hanging off an FW.

Trying to figure out the analogous way to set up an:

Active If: "PageCount(ID)>CurrentPage"

So if on page 1, the "Previous" button is not available, and same
thing on the last page attached to the FW.



I took a peek at the default interface, but the buttons seem to stay active,
they just don't navigate anywhere at the end of "travel".



















Subject:
RE: [Xerte] Controlling Nav buttons

Date: Fri, 20 Nov 2009 07:46:11 -0800

From: Paul.Swanson at harlandfs.com

To: xerte at lists.nottingham.ac.uk



I use a Decision icon to hold
content while on a page. I navigate through the Decision icon pages until all
of the content has been displayed, then exit the Decision icon. I have my Next
button interaction following the Decision icon, so it isn’t displayed until you
exit.

 

Paul

 







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 7:26 AM

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.





 















Bing brings you maps, menus, and reviews
organized in one place. Try
it now.



 











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



 







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

 		 	   		  
_________________________________________________________________
Hotmail: Trusted email with Microsoft's powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141664/direct/01/
http://clk.atdmt.com/GBL/go/177141664/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.nottingham.ac.uk/pipermail/xerte/attachments/20091120/26024b2b/attachment.html