Having a "brain freeze" moment. In theory, the current, next, and previous variables should be accessible from within a fileiterator. But next and previous seem to be void or null at all times - only current is defined. I'm not talking about something in slide.htt - this is within a fileiterator in index.htt. For example, these lines in index.htt always come back null:
Haven’t tried it, not fired up the Mac yet, but what about the ja:enter tag?
No, this isn't about folder variables.
I could do this manually, of course - create an array based on currentObject.getChildren() before entering the iterator, and then index into it while iterating. But there seems to be something wrong with the defined variables.
I think it is just that previous/next are not defined, despite the manual saying so
That's what my tests are telling me. Oddly, however, currentis defined.
ETA: Happily, I don't really need it after all - there's an easier way to do what I'm trying to do. So, if it's just a matter of updating the manual, that would be good enough for now. I don't think anyone has ever tried to use those variables in a fileiterator before. They work OK in slide.htt, which is where you're more likely to need them.
So, if it's just a matter of updating the manual, that would be good enough for now. I don't think anyone has ever tried to use those variables in a fileiterator before. They work OK in slide.htt, which is where you're more likely to need them.
Manual updated. Last time this came up appears to have been with the release of jAlbum 9.4 in 2011.
I'll be curious to see what David has to say about it.
The only references I could find to these variables all involved using them within slide.htt. I use it in a couple of skins to preload slide images - makes loading of the next page, like mydog.html, a lot quicker, since mydog.jpg is already in cache before you get to the page.
I checked the source code. It's apparently so that "next" and "previous" have only been defined for slide pages so please update the docs. I could naturally adjust this for the future on popular demand. It however seems that demand has been rather weak so far :-D