PC SOFT

FOROS PROFESIONALES
WINDEVWEBDEV y WINDEV Mobile

Inicio → WINDEV Mobile 2024 → WM19/WinCE - Scanner / Validation help
WM19/WinCE - Scanner / Validation help
Iniciado por Dave, 06,jul. 2015 14:07 - 2 respuestas
Publicado el 06,julio 2015 - 14:07
Hi all

I have an unusual issue with a mobile project running WM19 / WinCE 6.1

I have a window that has EDT fields that the user populates by scanning barcode, this need to then move through the screens (each screen being a plane) I have a <PREV> and <NEXT> button at the bottom of each screen (pane) with the next attributes set to 'validate' and the code behind the button validates the contact of the field, moves the plane to next screen and focus user input to next field. (a bit like a wizard style entry)

Some options scans/fields move the user on when he scans the barcode and some don't. I though that i had fixed one of the issues as i had it working on my hand held (Zebra Workabout PRO 4) but on the clients, who has the same device, it doesn't

On the screens that have an issue, if you manually select next then move back to the input field, the next scan correctly runs the next code 'on click' and moves to the next plane ???

Also by redelivering the install to the client, some screens that did move on now dont even though i havent changed any of the code for that window.

so my question is has anyone else experiences any weird issues with regards to scanning barcodes for an input field and running the 'on click' code of a button with 'validate' property set? Any help or ideas would be greatly appreciated

Kindest regards

Dave
Publicado el 06,julio 2015 - 14:49
Hi Dave,

the difference between your case and the customer may just be a
difference in the scanner settings...

On some of them you have to select ANSI or UNICODE, and if you don't
have the right one, the CR return may be interpreted wrongly (as the
number of bytes is doubled in unicode)

Best regards

--
Fabrice Harari
International WinDev, WebDev and WinDev mobile Consulting

Already there: WXShowroom.com, WXReplication (open source)
Coming soon: WXEDM (open source)
More information on http://www.fabriceharari.com
Publicado el 06,julio 2015 - 15:43
Fabrice Harari wrote:
Hi Dave,

the difference between your case and the customer may just be a
difference in the scanner settings...

On some of them you have to select ANSI or UNICODE, and if you don't
have the right one, the CR return may be interpreted wrongly (as the
number of bytes is doubled in unicode)

Best regards

--
Fabrice Harari
International WinDev, WebDev and WinDev mobile Consulting

Already there: WXShowroom.com, WXReplication (open source)
Coming soon: WXEDM (open source)
More information on http://www.fabriceharari.com


Hi Fabrice

Many thanks for your reply.

We have solved the customers issue being different, as you pointed out, one of the settings was different.

I do however have some issues the same as the customer where the the button click does not fire after the scan on some planes but some do.

On piece of code i did find:-

mywindow..plane = 2
setfocus(edt_scanfield2)

if <test> = true then
mywindow..plane = 3
setfocus(edt_scanfield3)
end

on plane 3 then next button didn't auto click after scan! changed code to:


if <test> = true then
mywindow..plane = 3
setfocus(edt_scanfield3)
else
mywindow..plane = 2
setfocus(edt_scanfield2)
end

and all works as it should. Not sure why ?

cheers
Dave