Symbol/Motorola Developer Community

[Harry Simpson]

I've been flailing away writing for Symbol/Motorola Pocket PC devices for
almost 8 years now. I've often wished there was a community of developers
that could share methods and utilities and ideas of architecting for these
devices.

I know there are a bunch of you out there.

I write in VB.NET in VS2008 using CF2 due to Zebra SDK 1.7 requirements,
Symbol SDK 1.6, 3.5 Compact Edition
and deploy to MC70's and use Zebra 220 Plus printers (TCP, BT, and Wired)

Anyone else out there and want to network?

Harry Simpson
(e-mail address removed)

 

[Ron Weiner]

Hi Harry

I have been working with Symbol MC50's for almost 2 years. I am also using
VB.net though still using Studio 03 and CF1.0. We are using the Symbol 1.7
SDK and use Citizen CMP-10 printers via IRDA and occasionally Wired RS-232.

It's been a while since I have been to Symbol's (oops Motorola's) Developer
site, but there was not much of an active community there as I recall. I
have been mostly pleased with the support delivered directly by Symbol in
the past when I needed it. Haven't a clue what is going on there today. We
have basically one product that we deliver using the MC50, and it is has
matured nicely over the last 12 months with minor upgrades and bug fixes.
We are looking at a round of new feature implementation later this year, so
it'd be nice to have a place to go for help/advice.

Ron W

 

[Harry Simpson]

Well Ron you haven't missed much on the developer site at Symbol/Motorola.
In fact if you left a message there 2 years ago chances are it hasn't had a
response yet....
The new Symbol 1.7 SDK and in particular the way they handle scans is much
improved but I've noticed an increased lag between the scan and the audible
beep with the new stuff for some reason. It's one of the those things that
doesn't bother me til it happens and then i quickly forget to add it to my
todo list...
Perhaps a blog that the number of us interested could all post to. I'd
start it and send out the credentials if interested.

Harry

 

[arohulich]

Hi Harry

I have been working with Symbol MC50's for almost 2 years.  I am also using
VB.net though still using Studio 03 and CF1.0.  We are using the Symbol1.7
SDK and use Citizen CMP-10 printers via IRDA and occasionally Wired RS-232.

It's been a while since I have been to Symbol's (oops Motorola's) Developer
site, but there was not much of an active community there as I recall. I
have been mostly pleased with the support delivered directly by Symbol in
the past when I needed it.  Haven't a clue what is going on there today..  We
have basically one product that we deliver using the MC50, and it is has
matured nicely over the last 12 months with minor upgrades and bug fixes.
We are looking at a round of new feature implementation later this year, so
it'd be nice to have a place to go for help/advice.

Ron W

Hi Harry,

I just recently started programming on the MC50. My previous
experience has been on Dell Axim Pocket PCs. I started back in 2001
using EVB and have upgraded along with the Studio and Dot Net CF. I am
currently using Studio 2005 and have been very pleased so far.

I am also using Symbol SDK 1.7 which seems to work fine. I am having
one problem which someone from the group may be able to assist me
with. Even though I followed the Hello World programs in the SDK
documentation I am getting an error after I terminate my application
on the MC50 and attempt to restart the application. The error occurs
when I attempt to enable the scanner. If I do a warm reset the error
does not occur. Any thoughts on this error? The error indicates
SCAN_Enable. I thought I was properly disposing of all the scanner
objects along with the eventhandler, but I still get the error after
one time running my applcation. Thanks in advance for any help you can
give me on this.

Alan Rohulich

 

[Paul G. Tobey [eMVP]]

Define "terminate my application". You did what? Clicked the X icon? If
so, that doesn't terminate anything. Make sure you tell us what you've done
so far and what the results were.

Paul T.

-----

Hi Harry,

I just recently started programming on the MC50. My previous
experience has been on Dell Axim Pocket PCs. I started back in 2001
using EVB and have upgraded along with the Studio and Dot Net CF. I am
currently using Studio 2005 and have been very pleased so far.

I am also using Symbol SDK 1.7 which seems to work fine. I am having
one problem which someone from the group may be able to assist me
with. Even though I followed the Hello World programs in the SDK
documentation I am getting an error after I terminate my application
on the MC50 and attempt to restart the application. The error occurs
when I attempt to enable the scanner. If I do a warm reset the error
does not occur. Any thoughts on this error? The error indicates
SCAN_Enable. I thought I was properly disposing of all the scanner
objects along with the eventhandler, but I still get the error after
one time running my applcation. Thanks in advance for any help you can
give me on this.

Alan Rohulich

 

[arohulich]

Define "terminate my application".  You did what?  Clicked the X icon?  If
so, that doesn't terminate anything.  Make sure you tell us what you'vedone
so far and what the results were.

Paul T.

-----

Hi Harry,

I just recently started programming on the MC50. My previous
experience has been on Dell Axim Pocket PCs. I started back in 2001
using EVB and have upgraded along with the Studio and Dot Net CF. I am
currently using Studio 2005 and have been very pleased so far.

I am also using Symbol SDK 1.7 which seems to work fine. I am having
one problem which someone from the group may be able to assist me
with. Even though I followed the Hello World programs in the SDK
documentation I am getting an error after I terminate my application
on the MC50 and attempt to restart the application. The error occurs
when I attempt to enable the scanner. If I do a warm reset the error
does not occur. Any thoughts on this error? The error indicates
SCAN_Enable. I thought I was properly disposing of all the scanner
objects along with the eventhandler, but I still get the error after
one time running my applcation. Thanks in advance for any help you can
give me on this.

Alan Rohulich

By terminate I mean that as the user taps the Ok on the MC50 a form
onclosing event checks for active threads, and once all active threads
have been stopped the following code is executed

myreader,actions.flush()
myreader.actions.disable()
myreader.dispose()
myreaderdata.dispose()

then an me.close is executed.

 

[Paul G. Tobey [eMVP]]

OK, so Remote Process Viewer wouldn't show it, then, just to be sure? If
that's the case, it would seem that Symbol is persisting the state of the
scanner, separate from its state within your code. Do the Hello, World
examples from Symbol suffer from this problem?

Paul T.

Define "terminate my application". You did what? Clicked the X icon? If
so, that doesn't terminate anything. Make sure you tell us what you've
done
so far and what the results were.

Paul T.

-----

Hi Harry,

I just recently started programming on the MC50. My previous
experience has been on Dell Axim Pocket PCs. I started back in 2001
using EVB and have upgraded along with the Studio and Dot Net CF. I am
currently using Studio 2005 and have been very pleased so far.

I am also using Symbol SDK 1.7 which seems to work fine. I am having
one problem which someone from the group may be able to assist me
with. Even though I followed the Hello World programs in the SDK
documentation I am getting an error after I terminate my application
on the MC50 and attempt to restart the application. The error occurs
when I attempt to enable the scanner. If I do a warm reset the error
does not occur. Any thoughts on this error? The error indicates
SCAN_Enable. I thought I was properly disposing of all the scanner
objects along with the eventhandler, but I still get the error after
one time running my applcation. Thanks in advance for any help you can
give me on this.

Alan Rohulich

By terminate I mean that as the user taps the Ok on the MC50 a form
onclosing event checks for active threads, and once all active threads
have been stopped the following code is executed

myreader,actions.flush()
myreader.actions.disable()
myreader.dispose()
myreaderdata.dispose()

then an me.close is executed.

 

[arohulich]

OK, so Remote Process Viewer wouldn't show it, then, just to be sure?  If
that's the case, it would seem that Symbol is persisting the state of the
scanner, separate from its state within your code.  Do the Hello, World
examples from Symbol suffer from this problem?

Paul T.








By terminate I mean that as the user taps the Ok on the MC50 a form
onclosing event checks for active threads, and once all active threads
have been stopped the following code is executed

myreader,actions.flush()
myreader.actions.disable()
myreader.dispose()
myreaderdata.dispose()

then an me.close is executed.- Hide quoted text -

- Show quoted text -

I am using the Hello World example almost verbatim. The only
difference is that I have a sleeping thread that needs to be stopped
prior to disposing the scanners objects. Maybe that is why the scanner
state is not the same. This may be a dumb question, but should I be
executing the code prior to stopping the thread via control invoke to
be at the same thread level / state?

 

[Paul G. Tobey [eMVP]]

No, you don't have to do anything, generally (I don't know how you're
stopping your thread), to notify the thread that it's time to exit. I
generally leave threads sitting either in WaitOne() sorts of things where
the event on which it is waiting will be Set() by the outside code to exit
the thread, or in other blocked calls, specific to the thread's job (in
which case, I set an event, then unblock the thread, maybe by closing the
socket it's waiting on, closing the serial port it's waiting on, etc.) The
thread unblocks, usually with an exception, handles the exception suitably,
then checks the event (WaitOne(0)), realizes that it's time to exit, and
does. If you run this program in the debugger, does the debugger think that
the application has exited, or does it wait for the thread to exit forever?
Does Remote Process Viewer still show the process?

Paul T.

OK, so Remote Process Viewer wouldn't show it, then, just to be sure? If
that's the case, it would seem that Symbol is persisting the state of the
scanner, separate from its state within your code. Do the Hello, World
examples from Symbol suffer from this problem?

Paul T.








By terminate I mean that as the user taps the Ok on the MC50 a form
onclosing event checks for active threads, and once all active threads
have been stopped the following code is executed

myreader,actions.flush()
myreader.actions.disable()
myreader.dispose()
myreaderdata.dispose()

then an me.close is executed.- Hide quoted text -

- Show quoted text -

I am using the Hello World example almost verbatim. The only
difference is that I have a sleeping thread that needs to be stopped
prior to disposing the scanners objects. Maybe that is why the scanner
state is not the same. This may be a dumb question, but should I be
executing the code prior to stopping the thread via control invoke to
be at the same thread level / state?

 

[arohulich]

No, you don't have to do anything, generally (I don't know how you're
stopping your thread), to notify the thread that it's time to exit.  I
generally leave threads sitting either in WaitOne() sorts of things where
the event on which it is waiting will be Set() by the outside code to exit
the thread, or in other blocked calls, specific to the thread's job (in
which case, I set an event, then unblock the thread, maybe by closing the
socket it's waiting on, closing the serial port it's waiting on, etc.)  The
thread unblocks, usually with an exception, handles the exception suitably,
then checks the event (WaitOne(0)), realizes that it's time to exit, and
does.  If you run this program in the debugger, does the debugger thinkthat
the application has exited, or does it wait for the thread to exit forever?
Does Remote Process Viewer still show the process?

Paul T.

OK, so Remote Process Viewer wouldn't show it, then, just to be sure? If
that's the case, it would seem that Symbol is persisting the state of the
scanner, separate from its state within your code. Do the Hello, World
examples from Symbol suffer from this problem?

Paul T.

<[email protected]> wrote in message

On Jun 18, 12:08 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:

Define "terminate my application". You did what? Clicked the X icon? If
so, that doesn't terminate anything. Make sure you tell us what you've
done
so far and what the results were.
Paul T.
-----
Hi Harry,
I just recently started programming on the MC50. My previous
experience has been on Dell Axim Pocket PCs. I started back in 2001
using EVB and have upgraded along with the Studio and Dot Net CF. I am
currently using Studio 2005 and have been very pleased so far.
I am also using Symbol SDK 1.7 which seems to work fine. I am having
one problem which someone from the group may be able to assist me
with. Even though I followed the Hello World programs in the SDK
documentation I am getting an error after I terminate my application
on the MC50 and attempt to restart the application. The error occurs
when I attempt to enable the scanner. If I do a warm reset the error
does not occur. Any thoughts on this error? The error indicates
SCAN_Enable. I thought I was properly disposing of all the scanner
objects along with the eventhandler, but I still get the error after
one time running my applcation. Thanks in advance for any help you can
give me on this.
Alan Rohulich

By terminate I mean that as the user taps the Ok on the MC50 a form
onclosing event checks for active threads, and once all active threads
have been stopped the following code is executed

then an me.close is executed.- Hide quoted text -

- Show quoted text -

I am using the Hello World example almost verbatim. The only
difference is that I have a sleeping thread that needs to be stopped
prior to disposing the scanners objects. Maybe that is why the scanner
state is not the same. This may be a dumb question, but should I be
executing the code prior to stopping the thread via control invoke to
be at the same thread level  / state?- Hide quoted text -

- Show quoted text -

I am executing it on the debugger and it seems to exit normally with
nothing left running.

 

[Paul G. Tobey [eMVP]]

Hmmm. Can't explain that. You're tracing through the calls that shut
everything down, as far as Symbol is concerned? You've set a breakpoint
just before the thread exits to make sure that it's leaving? And Remote
Process Viewer no longer shows the process?

Paul T.

No, you don't have to do anything, generally (I don't know how you're
stopping your thread), to notify the thread that it's time to exit. I
generally leave threads sitting either in WaitOne() sorts of things where
the event on which it is waiting will be Set() by the outside code to exit
the thread, or in other blocked calls, specific to the thread's job (in
which case, I set an event, then unblock the thread, maybe by closing the
socket it's waiting on, closing the serial port it's waiting on, etc.) The
thread unblocks, usually with an exception, handles the exception
suitably,
then checks the event (WaitOne(0)), realizes that it's time to exit, and
does. If you run this program in the debugger, does the debugger think
that
the application has exited, or does it wait for the thread to exit
forever?
Does Remote Process Viewer still show the process?

Paul T.

OK, so Remote Process Viewer wouldn't show it, then, just to be sure? If
that's the case, it would seem that Symbol is persisting the state of
the
scanner, separate from its state within your code. Do the Hello, World
examples from Symbol suffer from this problem?

Paul T.

<[email protected]> wrote in message

On Jun 18, 12:08 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:

Define "terminate my application". You did what? Clicked the X icon?
If
so, that doesn't terminate anything. Make sure you tell us what you've
done
so far and what the results were.
Paul T.
-----
Hi Harry,
I just recently started programming on the MC50. My previous
experience has been on Dell Axim Pocket PCs. I started back in 2001
using EVB and have upgraded along with the Studio and Dot Net CF. I am
currently using Studio 2005 and have been very pleased so far.
I am also using Symbol SDK 1.7 which seems to work fine. I am having
one problem which someone from the group may be able to assist me
with. Even though I followed the Hello World programs in the SDK
documentation I am getting an error after I terminate my application
on the MC50 and attempt to restart the application. The error occurs
when I attempt to enable the scanner. If I do a warm reset the error
does not occur. Any thoughts on this error? The error indicates
SCAN_Enable. I thought I was properly disposing of all the scanner
objects along with the eventhandler, but I still get the error after
one time running my applcation. Thanks in advance for any help you can
give me on this.
Alan Rohulich

By terminate I mean that as the user taps the Ok on the MC50 a form
onclosing event checks for active threads, and once all active threads
have been stopped the following code is executed

then an me.close is executed.- Hide quoted text -

- Show quoted text -

I am using the Hello World example almost verbatim. The only
difference is that I have a sleeping thread that needs to be stopped
prior to disposing the scanners objects. Maybe that is why the scanner
state is not the same. This may be a dumb question, but should I be
executing the code prior to stopping the thread via control invoke to
be at the same thread level / state?- Hide quoted text -

- Show quoted text -

I am executing it on the debugger and it seems to exit normally with
nothing left running.

 

[arohulich]

Hmmm.  Can't explain that.  You're tracing through the calls that shut
everything down, as far as Symbol is concerned?  You've set a breakpoint
just before the thread exits to make sure that it's leaving?  And Remote
Process Viewer no longer shows the process?

Paul T.

No, you don't have to do anything, generally (I don't know how you're
stopping your thread), to notify the thread that it's time to exit. I
generally leave threads sitting either in WaitOne() sorts of things where
the event on which it is waiting will be Set() by the outside code to exit
the thread, or in other blocked calls, specific to the thread's job (in
which case, I set an event, then unblock the thread, maybe by closing the
socket it's waiting on, closing the serial port it's waiting on, etc.) The
thread unblocks, usually with an exception, handles the exception
suitably,
then checks the event (WaitOne(0)), realizes that it's time to exit, and
does. If you run this program in the debugger, does the debugger think
that
the application has exited, or does it wait for the thread to exit
forever?
Does Remote Process Viewer still show the process?

Paul T.

<[email protected]> wrote in message

On Jun 18, 3:21 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:

OK, so Remote Process Viewer wouldn't show it, then, just to be sure?If
that's the case, it would seem that Symbol is persisting the state of
the
scanner, separate from its state within your code. Do the Hello, World
examples from Symbol suffer from this problem?
Paul T.
On Jun 18, 12:08 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:
Define "terminate my application". You did what? Clicked the X icon?
If
so, that doesn't terminate anything. Make sure you tell us what you've
done
so far and what the results were.
Paul T.
-----
Hi Harry,
I just recently started programming on the MC50. My previous
experience has been on Dell Axim Pocket PCs. I started back in 2001
using EVB and have upgraded along with the Studio and Dot Net CF. Iam
currently using Studio 2005 and have been very pleased so far.
I am also using Symbol SDK 1.7 which seems to work fine. I am having
one problem which someone from the group may be able to assist me
with. Even though I followed the Hello World programs in the SDK
documentation I am getting an error after I terminate my application
on the MC50 and attempt to restart the application. The error occurs
when I attempt to enable the scanner. If I do a warm reset the error
does not occur. Any thoughts on this error? The error indicates
SCAN_Enable. I thought I was properly disposing of all the scanner
objects along with the eventhandler, but I still get the error after
one time running my applcation. Thanks in advance for any help you can
give me on this.
Alan Rohulich
By terminate I mean that as the user taps the Ok on the MC50 a form
onclosing event checks for active threads, and once all active threads
have been stopped the following code is executed
myreader,actions.flush()
myreader.actions.disable()
myreader.dispose()
myreaderdata.dispose()
then an me.close is executed.- Hide quoted text -
- Show quoted text -

I am using the Hello World example almost verbatim. The only
difference is that I have a sleeping thread that needs to be stopped
prior to disposing the scanners objects. Maybe that is why the scanner
state is not the same. This may be a dumb question, but should I be
executing the code prior to stopping the thread via control invoke to
be at the same thread level / state?- Hide quoted text -

- Show quoted text -

I am executing it on the debugger and it seems to exit normally with
nothing left running.- Hide quoted text -

- Show quoted text -

Sorry for the delay in replying. I had some other high priority tasks
to handle before I could continue debugging this error. I did as you
suggested and ran the remote process viewer and it appears that after
my applications exits there remains a process (edm.exe) that is still
running on the device. Any thoughts on how to terminate that leftover
process?
Thanks,
Alan R

 

[Paul G. Tobey [eMVP]]

edm.exe/edm2.exe is part of the debugger connectivity with the device so, to
try to make future deploy/debug operations faster, it's not going to shut
that down every time. I suppose that, if you exit Visual Studio, it will go
away, but it's not the problem; don't worry about it.

If your EXE isn't listed as still running, you're fine and you'll need to
consult with Symbol about what's causing the error. As mentioned, comparing
your code to sample code that works when run multiple times, is the
most-likely thing to expose the problem.

Paul T.

Hmmm. Can't explain that. You're tracing through the calls that shut
everything down, as far as Symbol is concerned? You've set a breakpoint
just before the thread exits to make sure that it's leaving? And Remote
Process Viewer no longer shows the process?

Paul T.

No, you don't have to do anything, generally (I don't know how you're
stopping your thread), to notify the thread that it's time to exit. I
generally leave threads sitting either in WaitOne() sorts of things
where
the event on which it is waiting will be Set() by the outside code to
exit
the thread, or in other blocked calls, specific to the thread's job (in
which case, I set an event, then unblock the thread, maybe by closing
the
socket it's waiting on, closing the serial port it's waiting on, etc.)
The
thread unblocks, usually with an exception, handles the exception
suitably,
then checks the event (WaitOne(0)), realizes that it's time to exit, and
does. If you run this program in the debugger, does the debugger think
that
the application has exited, or does it wait for the thread to exit
forever?
Does Remote Process Viewer still show the process?

Paul T.

<[email protected]> wrote in message

On Jun 18, 3:21 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:

OK, so Remote Process Viewer wouldn't show it, then, just to be sure?
If
that's the case, it would seem that Symbol is persisting the state of
the
scanner, separate from its state within your code. Do the Hello, World
examples from Symbol suffer from this problem?
Paul T.
On Jun 18, 12:08 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:
Define "terminate my application". You did what? Clicked the X icon?
If
so, that doesn't terminate anything. Make sure you tell us what
you've
done
so far and what the results were.
Paul T.
-----
Hi Harry,
I just recently started programming on the MC50. My previous
experience has been on Dell Axim Pocket PCs. I started back in 2001
using EVB and have upgraded along with the Studio and Dot Net CF. I
am
currently using Studio 2005 and have been very pleased so far.
I am also using Symbol SDK 1.7 which seems to work fine. I am having
one problem which someone from the group may be able to assist me
with. Even though I followed the Hello World programs in the SDK
documentation I am getting an error after I terminate my application
on the MC50 and attempt to restart the application. The error occurs
when I attempt to enable the scanner. If I do a warm reset the error
does not occur. Any thoughts on this error? The error indicates
SCAN_Enable. I thought I was properly disposing of all the scanner
objects along with the eventhandler, but I still get the error after
one time running my applcation. Thanks in advance for any help you
can
give me on this.
Alan Rohulich
By terminate I mean that as the user taps the Ok on the MC50 a form
onclosing event checks for active threads, and once all active threads
have been stopped the following code is executed
myreader,actions.flush()
myreader.actions.disable()
myreader.dispose()
myreaderdata.dispose()
then an me.close is executed.- Hide quoted text -
- Show quoted text -

I am using the Hello World example almost verbatim. The only
difference is that I have a sleeping thread that needs to be stopped
prior to disposing the scanners objects. Maybe that is why the scanner
state is not the same. This may be a dumb question, but should I be
executing the code prior to stopping the thread via control invoke to
be at the same thread level / state?- Hide quoted text -

- Show quoted text -

I am executing it on the debugger and it seems to exit normally with
nothing left running.- Hide quoted text -

- Show quoted text -

Sorry for the delay in replying. I had some other high priority tasks
to handle before I could continue debugging this error. I did as you
suggested and ran the remote process viewer and it appears that after
my applications exits there remains a process (edm.exe) that is still
running on the device. Any thoughts on how to terminate that leftover
process?
Thanks,
Alan R

 

[arohulich]

edm.exe/edm2.exe is part of the debugger connectivity with the device so,to
try to make future deploy/debug operations faster, it's not going to shut
that down every time.  I suppose that, if you exit Visual Studio, it will go
away, but it's not the problem; don't worry about it.

If your EXE isn't listed as still running, you're fine and you'll need to
consult with Symbol about what's causing the error.  As mentioned, comparing
your code to sample code that works when run multiple times, is the
most-likely thing to expose the problem.

Paul T.

Hmmm. Can't explain that. You're tracing through the calls that shut
everything down, as far as Symbol is concerned? You've set a breakpoint
just before the thread exits to make sure that it's leaving? And Remote
Process Viewer no longer shows the process?

Paul T.

<[email protected]> wrote in message

On Jun 18, 4:12 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:

No, you don't have to do anything, generally (I don't know how you're
stopping your thread), to notify the thread that it's time to exit. I
generally leave threads sitting either in WaitOne() sorts of things
where
the event on which it is waiting will be Set() by the outside code to
exit
the thread, or in other blocked calls, specific to the thread's job (in
which case, I set an event, then unblock the thread, maybe by closing
the
socket it's waiting on, closing the serial port it's waiting on, etc.)
The
thread unblocks, usually with an exception, handles the exception
suitably,
then checks the event (WaitOne(0)), realizes that it's time to exit, and
does. If you run this program in the debugger, does the debugger think
that
the application has exited, or does it wait for the thread to exit
forever?
Does Remote Process Viewer still show the process?
Paul T.
On Jun 18, 3:21 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:
OK, so Remote Process Viewer wouldn't show it, then, just to be sure?
If
that's the case, it would seem that Symbol is persisting the state of
the
scanner, separate from its state within your code. Do the Hello, World
examples from Symbol suffer from this problem?
Paul T.
On Jun 18, 12:08 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:
Define "terminate my application". You did what? Clicked the X icon?
If
so, that doesn't terminate anything. Make sure you tell us what
you've
done
so far and what the results were.
Paul T.
-----
Hi Harry,
I just recently started programming on the MC50. My previous
experience has been on Dell Axim Pocket PCs. I started back in 2001
using EVB and have upgraded along with the Studio and Dot Net CF.I
am
currently using Studio 2005 and have been very pleased so far.
I am also using Symbol SDK 1.7 which seems to work fine. I am having
one problem which someone from the group may be able to assist me
with. Even though I followed the Hello World programs in the SDK
documentation I am getting an error after I terminate my application
on the MC50 and attempt to restart the application. The error occurs
when I attempt to enable the scanner. If I do a warm reset the error
does not occur. Any thoughts on this error? The error indicates
SCAN_Enable. I thought I was properly disposing of all the scanner
objects along with the eventhandler, but I still get the error after
one time running my applcation. Thanks in advance for any help you
can
give me on this.
Alan Rohulich
By terminate I mean that as the user taps the Ok on the MC50 a form
onclosing event checks for active threads, and once all active threads
have been stopped the following code is executed
myreader,actions.flush()
myreader.actions.disable()
myreader.dispose()
myreaderdata.dispose()
then an me.close is executed.- Hide quoted text -
- Show quoted text -
I am using the Hello World example almost verbatim. The only
difference is that I have a sleeping thread that needs to be stopped
prior to disposing the scanners objects. Maybe that is why the scanner
state is not the same. This may be a dumb question, but should I be
executing the code prior to stopping the thread via control invoke to
be at the same thread level / state?- Hide quoted text -
- Show quoted text -

I am executing it on the debugger and it seems to exit normally with
nothing left running.- Hide quoted text -

- Show quoted text -

Sorry for the delay in replying. I had some other high priority tasks
to handle before I could continue debugging this error. I did as you
suggested and ran the remote process viewer and it appears that after
my applications exits there remains a process (edm.exe) that is still
running on the device. Any thoughts on how to terminate that leftover
process?
Thanks,
Alan R- Hide quoted text -

- Show quoted text -

Yes, between replies I ran my application without the debugger and
found the edm.exe does not exist. However the problem still exists. I
was attempting to trace the different threads to see what might be
different before and after running my barcode scanning application. My
next best bet is to call Symbol/Motorola to get their help and see if
they have encountered this problem before. Thanks for all your help so
far on this,

Alan R

 

[arnodieter]

Hello Ron.

I'm developing on a Symbol MC7094 with VS2008 and Symbol SDK 1.7.

I detected that there seems to be some errors in the scanner handling from
Symbol. I erroneouly enabled the scanner more than once, which should not
harm anything, but after that my application did not close completely.
Programming an if (!scanner.enabled) does NOT solve the problem. I had to
asure, that I enable the scanner only once.
Since than on my application closes without any problems.
Hope this helps
Regards
Arno

 

[Seth ONeal]

Hi Harry,

I'm kind of a newbee to Symbol/Motorola Pocket PC development. I only have about 6 mos. or so experience. But I also am using .NET CF 2.0 (C#), I am using the Symbol 1.7 SDK.
My hardware is the MC75 and I am trying to get things to run with Zebra RW 420 printers.

I have found it quite a struggle (sometimes) to figure out how to get some things occomplished.

I would love to network with you guys.

Seth
(e-mail address removed)

 

[Ron Weiner]

I have been working with the Symbol MC50 for a couple of years. We are
using CF1, Symbol 1.7 SDK, Open Net CF 1.4, and InTheHand.Net.IrDA v1.6 (I
think).

The MC75 has lots more ways to communicate with printers than the lowly 50
does. I haven't the faintest idea of what interface(s) are available on the
Zebra RW420's.

Printing in our application is strictly optional, and most customers choose
to do without the hard copy. We are using either a wired Serial or wireless
IrDA connection to talk to Citizen CMP-10 and O'Neil MicroFlash2 portable
printers. We also support Generic HP laser and Canon inkjet desktop
printers using the same interfaces. Our application prints only formatted
text (no graphics) and basically just opens a port and sends bytes down it.
I have toyed with the idea to print using WiFi interface, but (for now at
least) we do not have a business case worthy of the development time it
might take.

There are a few Symbol guys that hang out here. Perhaps some one else will
chime in. There is certainly no one hanging out over at the Motorola site.
For all I know Motorola might have given up on it.

But there are a LOT of GREAT programmers that do hang out here. If you have
a specific question, just go ahead and fire away. I should not be surprised
in the least that at the minimum you get at least a hint for solving your
problem.

Ron Weiner

 

[nadia g]

Hello,
We are writing an application for MC50 and would like to connect and disconnect from the wireless only when we want to synch the data. What can I use to programmatically connect and disconnect from the wireless?

 

[Paul G. Tobey [eMVP]]

You mean that you want to enable/disable the WiFi on the specific device
based on what your program wants to do? Doesn't the MC50 have a device SDK
that has control over the WiFi in it? If not, you can use a combination of
my previous posts on the subject of "disable adapter" and OpenNETCF Smart
Device Framework, which you can get from www.opennetcf.com, to turn the
adapter driver on and off. Search the archives from here:

http://groups.google.com/group/microsoft.public.dotnet.framework.compactframework/topics

Paul T.

 

[Ron Weiner]

In the Symbol SDK you will find a Demo application in both C#
(CS_WirelessLANSample1) and VB (VB_WirelessLanSample1) that demonstates how
to control the wireless adapter in the MC50.

Rdub