I've created an interactive picture book of 127 pages in AID CS5. I've exported it to SWF Flash and created a proj exe.I'm working with Microsoft Vista as the OS of my computer.I'm using the page turn function in AID CS5.
Obviously to save people pressing a button 127 times to get to the end of a book, I've placed some buttons in the document that jump 10 pages ahead. However, while some of these buttons work properly, other buttons, even though I place the 'turn to page >>>>' command in the button panel, do not and the button panel overrides my instructions and tells the button to return to page 1 of the book.
It's driving me mad and I'm sorry if this question has been asked on this forum before - I did search before I created this thread - but does anyone know what my problem is and what, if any, are the solutions.
Thanks in advance.
Check out eDocker2 Desktop Publisher (http://www.edocker.com)
It may save lot´s of work for you. It creates navigation tools automatically for you.
You can use same SWF you exported from InDesign with eDocker.
Here´s one sample:
If you have double checked the attributes of a button, and they're correct, and it still misbehaves after export, I would suggest exporting idml of the indesign document. Then open idml and export a new .swf to see if this fixes button issue.
I'll try that tomorrow morning. Is there any technical reason that the button (s) would behave like this, has anyone else had similar problems?
This is the first time for me, but I've always felt a bit suspicious about the button's attributes since one sets them and rather than have a function to confirm the instructions and set those instructions in stone, one moves on to another activity outside of that button and hopes that the instructions you have set will be followed through by the button.
I've had documents (with many buttons) after export not work correctly and the idml method fixed the issue. While this may not be the most technical explanation, but when exporting to idml or inx, the structure of a file, including instructions of a button, will get re-written. This process can cleanup any corruptions that may have happened during things like: many saves, adding interactive elements - which adds to the complexity of the doc, etc.
@rodenthead – my experience with buttons and their targets are to hit "return" after editing a target. Otherwise the button could switch back to its old target address. I don't know if that applies to your workflow, but in case…