Ваши комментарии

Ok, cool. It was probably a weird server thing. Good to know about url not being an object property. Thanks, Ian!
Rapid follow-up:

It's possible it's a server/hosting issue, maybe? As a last ditch post-midnight effort, I made a copy of the file on a different server and pointed the app there. It's loading all perfect now. Also, the [object:X.url] alert still shows "nil" so maybe that's not a legit object variable.

Interesting.
I know, I know... :) I think I confused it with size='fit'. It won't happen again. :)
Well, that's just magical. How did I not know that this exists/how to properly use it? This changes everything! :) Thanks, Ian!
Can I do anything that's the exact opposite of that? Same size font, but resizes text container? (Probably wishful thinking, but I'm just throwing it out there.)
Ah, of course, onscrollaway. Thanks!

Awesome. That could be pretty cool.

I'll check it out. I have it set at 256. Is that the max? And what does the value actually mean?
One more question: Is the gallery tag Retina-optimized? I'm seeing a little jaggedness along the angled side of a tile: https://www.dropbox.com/s/92gcbxua8f8...

Just wondering! :)
Ah, I was afraid of that. I noticed that if I triggered my action and turned my iPad 90° (and back, since my design isn't landscape optimized yet) it redrew the pager perfectly. This makes sense, but isn't practical, of course.

Just for clarification, here's how I have my pager laid out:

<pager>
<panel name="1" onclickup="open">
<panel name="1a"></panel>
</panel>
<panel name="2" onclickup="open">
<panel name="2a"></panel>
</panel>
<panel name="3" onclickup="open">
<panel name="3a"></panel>
</panel>
<panel name="4" onclickup="open">
<panel name="4a"></panel>
</panel>
</pager>


I could also structure it like this:

<pager>
<panel name="1" onclickup="open"></panel>
<panel name="1a"></panel>
<panel name="2" onclickup="open"></panel>
<panel name="2a"></panel>
<panel name="3" onclickup="open"></panel>
<panel name="3a"></panel>
<panel name="4" onclickup="open"></panel>
<panel name="4a"></panel>
</pager>


Another method I'm contemplating: my action could delete all the primary panels, and recreate them with the appropriate secondary panel in the mix. (Tapping on "1" deletes "1", "2", "3", and "4" then creates "1", "1a", "2", "3", and "4".) This is a little uglier code and probably a slightly slower experience, but it might work.

Looking forward to your example! Thanks, Ian!
Hey, just thought I'd chime in. I worked out my problem by using the Wavelength guys' custom number keyboards (https://getsatisfaction.com/rarewire/...). I modified them a bit by stripping out the currency button and transforming it to a decimal button (exact same concept as how the number buttons work).

Hope this helps!


Сервис поддержки клиентов работает на платформе UserEcho