Closed GoogleCodeExporter closed 9 years ago
This issue is created with test case project for the problems reported in
Issue: 1279.
Original comment by nir...@nvsoft.com
on 21 Jan 2015 at 5:39
Another observation is that, when we click from pin field to the amount
field(which is a decimal field), sometimes the decimal keyboard is shown and
then it gets replaced by the only numeric keyboard(without the decimal point
'.')
Original comment by nir...@nvsoft.com
on 27 Jan 2015 at 2:12
After fixing issue 1278, I can't reproduce this issue on the new VM. Fix will
be available in next update.
Original comment by st...@weblite.ca
on 27 Jan 2015 at 11:44
Has the new code updated on build server?
With the latest build, the sample project is still giving null pointer
exception as given in the stack trace below:
Jan 28 11:21:09 Rivans-ipad MyApplication[498] <Warning>:
java.lang.NullPointerException
at com_codename1_impl_ios_IOSImplementation_6.run:493
at com_codename1_ui_Display.processSerialCalls:1115
at com_codename1_ui_Display.edtLoopImpl:1059
at com_codename1_ui_Display.invokeAndBlock:1169
at com_codename1_ui_Display.invokeAndBlock:1204
at com_codename1_impl_ios_IOSImplementation.editString:510
at com_codename1_impl_CodenameOneImplementation.editStringImpl:289
at com_codename1_ui_Display.editString:1479
at com_codename1_ui_Display.editString:1451
at com_nvsoft_s2pay_pos_sawin_MyApplication_9_1.run:198
at com_codename1_ui_Display.processSerialCalls:1115
at com_codename1_ui_Display.edtLoopImpl:1059
at com_codename1_ui_Display.mainEDTLoop:965
at com_codename1_ui_RunnableWrapper.run:120
at com_codename1_impl_CodenameOneThread.run:176
at java_lang_Thread.runImpl:153
Jan 28 11:21:09 Rivans-ipad MyApplication[498] <Warning>:
Original comment by nir...@nvsoft.com
on 28 Jan 2015 at 5:55
No it hasn't. I'm not sure what Shai's schedule is for updating it. It may
be a few days.
Original comment by steve.ha...@codenameone.com
on 28 Jan 2015 at 6:30
Thanks Steve for the update. Any way to check the build server version, so that
we can know when new changes are applied to it? If not, would you please
announce on the discussion thread, so that I can verify the fix.
Original comment by nir...@nvsoft.com
on 28 Jan 2015 at 7:40
Original issue reported on code.google.com by
nir...@nvsoft.com
on 21 Jan 2015 at 5:37Attachments: