Hi all,
as U know i have Nokia E72 with full Qwerty keyboard. EditBox have only two inputmodes:
IM_STANDARD and IM_NUMBERS
so i can't write easily text to editboxes ??? - is any fix or trick to do that ???
thx for answer
Hi all,
as U know i have Nokia E72 with full Qwerty keyboard. EditBox have only two inputmodes:
IM_STANDARD and IM_NUMBERS
so i can't write easily text to editboxes ??? - is any fix or trick to do that ???
thx for answer
Yes, there's a trick: CharInput::setQwerty();
Fredrik, my Master - tell me please how can i use it in my code? I tried:
EditBox* editBox = new EditBox( etc... );
editBox->setQwerty(); -------------------------> error: 'class MAUI::EditBox' has no member named 'setQwerty'
i use MoSync 2.5(r1641)
This function has changed more than most, so it's easy to get confused. 
In revisions prior to 1653, you would do this:
CharInput::getCharInput().setQwerty(true);
In r1653 and later, you can also do this:
editBox->setInputMode(IM_QWERTY);
Fredrik --> tell me please, how is it?
I thought , that when U say "In revisions prior to 1653, you would do this:"
it should work in newest rev r1755. So i downloaded this now - and have error in:
editBox->setInputMode(IM_QWERTY); -----------------> : error: `IM_QWERTY' was not declared in this scope
i have on start
#include
#include
Sorry, my bad. This is more correct:
editBox->setInputMode(EditBox::IM_QWERTY);
Fredrik ---> U have right, now compilations goes OK, but...
unfortunetly it doesn't sems to work propelly with my Nokia E72. I allways have IM_NUMBERS mode
even if I set in constructor IM_STANDARD
it could be some bug for this Nokia Model ? or another one trick/switch ?
Where can i report another bug with my Nokia E72 - i tested yet r1750, r1752 and r1755. Any of them don't work propelly with Bluetooth discovery . I can only start - but next is absolutley nothing. (I add - it is only on physical phone E72, with emulator all work's OK)
from prior builds i tested yet: r767, r1566, r1645, r1685(now) .... they work's OK with the same code and BTListner. They can preety discover BTDevices and services.
and once more small bug in all tested builds by me except r767. In all this builds
maprofile.h for Nokia E72 have wrong screen size definition
#define MA_PROF_CONST_SCREENSIZE_X 240
#define MA_PROF_CONST_SCREENSIZE_Y 320
it should be
#define MA_PROF_CONST_SCREENSIZE_X 320
#define MA_PROF_CONST_SCREENSIZE_Y 240
i must always correct this file, restart IDE to it work propelly with on-screen emulator
can U help me ???
To report another bug, please start another thread. That way, any long-winded discussions will be properly separated. For now, though, I'll reply here.
Your Bluetooth problem is probably related to our new Permission settings. I've written a post on the subject.
Our profile database has the wrong screen size for the E72. We will fix it as soon as possible.
Fredrik --> Master
.... newest build r1755, is working with BT on my Nokia with good permision settings. Thanks a lot.
but maybe some more little help with this "Qwerty" problem on this Nokia. Like i see from build r1566 EditBox work ONLY in IM_NUMBERS mode
(fragment of my code: )
EditBox* editBox = new EditBox(0, 0, scrWidth-PADDING*2, 28, NULL, "abc", 0, gFont, true, false, 64, EditBox::IM_STANDARD);
(and always work's only in numbers mode)
any idea for fix this? or should i wait for next nightly build? 
I've now had enough time to run a test. This told me that our Qwerty support on S60 is not yet implemented.
I'm out of time today, but with any luck I can get it fixed tomorrow, which means you should see it in the nightly build of the 19th.
Fredrik --> U are my MASTER
.... I will waiting
IM_NUMBERS mode does not seem to allow input of decimal dot, i.e., you can not enter 0.5 to the EditBox with IM_NUMBERS mode.
Also in IM_NUMBERS mode, pressing "*" key will enter "+" in the box, maybe it should be a decimal dot ".", this will solve the problem entering decimal numbers.
You can change the keyboard mapping in NUMBERS mode by calling CharInput_setNumMapElement(). It's not very well documented at the moment, so you'll want to look at the source code to see how it works.