Problems with Symbol/Motorola SMDK 1.7 .Net

A

arnodieter

I know that this is not a symbol forum, but the support from Symbol is not
soooo good :-(. I also know that some developers here are working with
Symbol SMDK.

I'm working on an application for inventory which must run on a
Motorola(Symbol) MC1000. For development VS20008, CF2.0 and Symbol SMDK
V1.7.Net are used.

During programming and testing some question came up:

1. I'm using the Barcode design control. This control has a property called
"EnableScanner". While working with this control I detected that this
control misbehaves when it is switched to "true" more than once. This is a
not acceptable behaviour in my opinion! I can switch on LEDs e.g. how often
I wish, and the LEDs stay on and behave correct, what the barcode control
doesn't do! This issue should be solved.

2. In my application there are textboxes for entering EAN articlenumbers
(whith only EAN/UPC allowed), quantities (with no scanning allowed) and
storage locations (with only I2OF5 enabled). I thought I set "EnableScanner"
to false in the quantity field and that works. I worked, but in tests I
detected that it takes about 500ms to enable/disable the scanner. This is
much too long. So I took a look in the DLLs and found out that the control
is completly disposed recreated on disabling/enabling. That's not really
what I wanted!?

So how can I fast (runtime, not programming) enable/disable the scanner so
that the users can't scan in the quantity field?

3. Why isn't there a property "Enabled" which all other controls have and
that property fast eanbles and disables the scanner? See question 2...

4. For preventing the users switching to the alphamode on the MC1000
(handylike keyboard) I'm using the Symbol.Keyboard.KeyPad. This works fine
so far. But when my application is killed or crashes the event seems to be
active. This leads to a problem when my application is started again. In
creating the keypad I get an exception when I'm instantiating the keypad
with new keypad(). How can I solve this problem?

Best regards
 
R

RobRasti

I've worked with the SMDK before. Not the best device SDK compared to
other device manufacturers, but workable. What I have done in the
past is track a reference to the Scan Target field, and when the Scan
Event is triggered by the SMDK I decide where to put the data. This
allows you to turn on the scanner when the form loads and based on
focus allow input or ignore the input.

Hope this helps.
-Rob-
 
A

arnodieter

Thanks for this hint.

That will be my solution also, cause I got no better solution at the moment.

The Motorola/Symbol freaks are great: programming a SMDK and no support at
all (without contract - speaking money). That's the job I'm looking for...

Regards.
 
K

Kevin Matthews

same solution from me. Case out what textbox has focus when the scan event
is received. If it's the quantity field you can either ignore it or else
bash the user over the head with a message box.

good luck!

Kevin
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top