[Xerte] Some simple Qs and comments

[Riley Fred]

Thanks for that, Paul - I'd not have guessed that, but it does work, at
least the nextPage() method. Do you know if gotoPage() can take a unique
page id (eg gotoPage('A') or similar) rather than a number? This is
related to the next Q I'll be posting about hotspots. 

I've got to get into 'frameworks' as it looks like they're crucial to
building non-trivial applications. I'm still trying to get my head
around templates, though :(

Cheers

Fred Riley
Learning Technologist, School of Nursing, University of Nottingham
Vcard: http://www.nottingham.ac.uk/nursing/sonet/about/fr_uon.vcf  

> -----Original Message-----
> From: xerte-bounces at lists.nottingham.ac.uk 
> [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of 
> Paul Swanson
> Sent: 29 January 2008 18:42
> To: Xerte discussion list
> Subject: RE: [Xerte] Some simple Qs and comments
> 
> To respond to your main question, to navigate to the next 
> page I use a button interaction with the following in a script icon:
> rootIcon.nextPage();
> 
> In my specific case this navigates to the next page on the 
> Main Icon Flow, but you could navigate to any page on any 
> framework by using myFrameworkId.gotoPage(pageNumber). 
> pageNumber comes from the id.pages() property of the 
> framework, and, I expect, is zero-based, so pageNumber for 
> the first page would be 0, the second page would be 1, etc.
>