facebook

Aaargh!

💡
Our Forums Have Moved

For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub

  1. MobiOne Archive
  2.  > 
  3. Getting Help – General
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #338751 Reply

    Stu Wade
    Member

    Having just “advised” Publio Decio and Torben in threads below – I now find that having compiled my WebApp for the first time – I seem to have got both their problems myself. (Sorry guys)

    First – the white flash is FAR more pronounced in the native iOS compilation – but I can live with it.

    Second – using HTML in the send email worked perfectly in the WebApp – but is reproduced literally in the compiled version – this is absolutely critical to my application – HELP please.

    #338761

    Stu Wade
    Member

    OK – I can get the line-breaks back by using ‘\r’ or <lf> i.e. String.fromCharCode(10) — interestingly <cr> i.e. String.fromCharCode(12) does not seem to do anything.

    But — I need to force a monospace font — any ideas at all even completely off the wall ones greatly appreciated

    #338772

    Stu Wade
    Member

    @ Support,

    Do you have any idea why I get different behaviour from the WebApp – which transitions into the iPad mail client and displays and sends the email exactly as expected with mono spacing and typewriter formatting
    and the iOS App which displays a ‘new mail’ page on top of the App with no actual transition to the mail client – this new mail page is literal and not interpreted as html and sends just that i.e. “<html>……….” in the default font?

    I ask in the hope that the why may give some insight as to how to circumvent this.

    #338816

    Stu Wade
    Member

    Progress:

    The send formatted email problem seems to have been solved!
    See this thread http://www.genuitec.com/support-genuitec/viewtopic.php?f=8&t=5464

    Making a little progress on the white flash – making the first real page of the App as simple as possible appears to greatly ameliorate the problem – will report as this idea is progressed.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Aaargh!

You must be logged in to post in the forum log in