Just put a white rectangle that disappears on load.
It's not that big deal.

Hi penelope, I'm sorry but I'm not that familiar with the mobi format..so I guess you'll be on your own on this subject..

as I answered on the other post (I'll report it so that everyone in need can see) , I guess that's due to the dimensions of the miniatures..are you sure they ain't bigger than your general epub dimensions?

There might even be some undeclared maximum dimensions for miniature images..so you see..just try to resize them a little and let me know if that works!

mmmmmmh I didn't get it was about read aloud..anyway about what you asked on the cover image:

Did you used the right dimensions? Maybe your device isn't rendering them as they're too big, the fallback option implemented by pubCoder automatically uses the first page for the cover/miniature, by what I've experienced...

PS: consider that mostly the problem you can get from this GUI are dued to our errors in creating the right assets for the pages :) (I get these kinda errors in primis)

Was this what you meant?

That is completely wrong in this GUI environment.

PubCoder doesn't have a graphic engine (at least not one that you can use to change a button's shape) BUT you can do this (mine) solution:

-create 4 rectangles and shrink their height to 3-4 pixels -> that will give the feeling of a "line" (NB: it will be kinda hard move those obj around dragging them as they won't have much height....)

-dispose the 4 lines in the shape that you want (trapezoidal or whatever)

-create a completely blank / transparent button/shape/whatever

-put it over the shape you created

-give the actions you want on touch

Was this helpful?

PS: I didn't get the end of your sentence..not even in italian (and I'm italian) but if you explain I'll gladly answer if I know how to do that

PS: A little hint...Keep in mind that you don't actually need HD images to give the feeling of an actual HD image on an iPad...;)

Carlton is right, and, moreover, you should try to change the order of actions, maybe you added too many action on "page load" -> your device can't keep up to the quantity (and QUALITY) of your objects -> that's why you see the white flash: it's rendering overload

SuperNice Paolo!!! I needed this too and you gave me a quick version of whatever I would have done!
Thank you soooo much, really! :)

Paolo A If you need something quick and simple, you can obtain this as follows:
to Touch Down event add "Execute Javascript" action -> Open the code editor and add the following code:

$("#obj1234").stop();

Where "obj1234" is the id of the object you want to stop. You can get that ID by looking under the Levels Panel on the left (click on the # button on bottom right), or in the code editor you can use the snippet by selecting the object from the Level's panel.

Take into account that this "stop" action will interrupt all other actions you have eventually inserted following the move action on that or any other object.

Let me know if it works.

TOC renders automatically and there's no control over it, so I guess you have to change manually everything

PS: maybe there's something wrong about the notes and the weight that your code gives to them -> also pages appear in the TOC (that normally wouldn't happen and doesn't happen to me in my book without footnotes and such elements)

Sooooo I think the good way to do this (differently to inDesing that let you chose the way to render TOC) is to keep things as much simple as you can and then in a second moment change them manually after you finished your book..

mmmm..that sound to me more likely a "dimensions" problem.

A) did you implement your current font by the CSS option or did you change it manually in each text box?

B) Are you sure you chose the right dimensions of your app/epub from the start? (I mean even a slight change of 10 px can crash everything)

If you're right in both the cases then could be something like this (wrong) process:

• make a new text box
• use a font
• change the font manually and use one of the imported fonts
• > can't see the correct rendering

That could be due to the right box dimensions -> maybe you made a text box big enough for your first font, but then it ain't big enough for your new font -> rendering problem..

Let me know if I was clear enough / you need something else :)