×

Discussion Board

Results 1 to 4 of 4
  1. #1
    Super Contributor
    Join Date
    Mar 2003
    Posts
    1,733

    Can somebody teach me how to fix the problem "Entered text too long"

    Posted by Vilian Iliev, wili98@mail.search.bg
    on February 19, 2001 at 17:47

    This happens when my deck is more than 1393b (compiled). What is that bug from Nokia is that is true in real handset? What do I do if I have to put 4 Select's in one form to search? I can not undarstand why is this.

  2. #2
    Super Contributor
    Join Date
    Mar 2003
    Posts
    1,733

    RE: Can somebody teach me how to fix the problem "Entered text too long"

    Posted by Tom O, Tom@AFPWeb.Com
    on February 20, 2001 at 01:00

    Maybe a lot of the problem is the handset but there is a limitation on all handsets.

    The SELECT is processed on the Web server annd never sees the gateway (in pages like ASP, AFP, etc).

    The trick is to make your decks smaller. The uncompiled reccommended limit is 1492 Bytes.

  3. #3
    Super Contributor
    Join Date
    Mar 2003
    Posts
    1,733

    RE: Can somebody teach me how to fix the problem "Entered text too long"

    Posted by tp lee, tplee@ctiresources.com.my
    on February 20, 2001 at 05:40

    Try splitting your deck into few small decks. Please do not put all into one deck as this is not a good way to create a program. Split into small deck is a good way to track the errors, re-used decks, and etc.

    Before, you develop the program, probably you need to read some on WAP phones' technical reports, e.g Nokia 7110 does not support alignment in center/right.

  4. #4
    Super Contributor
    Join Date
    Mar 2003
    Posts
    1,733

    RE: Can somebody teach me how to fix the problem "Entered text too long"

    Posted by WAP Toolkit Team, info.wapbrowser@nokia.com
    on March 01, 2001 at 21:35

    If you are planning on supporting the 7110 handset as one of your target devices, you must keep your deck size below 1397. This is a limitation within the actual handset and a good benchmark for the "lowest common denominator" in deck size.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×