Controls do not seem to render correctly

Hello,

I am encountering strange problems in my current CF forms application.


Sometimes controls will be rendered incorrectly, e.g. a label being
rendered like a button - with a black border and a white background that
changes to black when clicked with the pen and changes back to white
afterwards. Once or twice the form itself showed the same behaviour.

At other times events simply won't be handled. For example, clicking on
the second tab of a tab control will highlight the selected tab as it
should, but the first tab will still be shown. Or buttons and menu
entries can be clicked (the controls do display the click event), but
the handlers won't be called...

Those problems do not occur on every form nor do they show on a given
form every time the form is displayed. So one form may work correctly
one time, but after restarting the application the very same form could
cause one of the mentioned problems.


The system does not show any error messages. Either the controls will no
longer handle any events, or the application exits without an error. In
that case Visual Studio shows the following message (even during tests
on an emulator):

"The remote connection to the device has been lost. Please verify the
device connection and restart debugging."

I am using Visual Studio 2005 Professional Edition and the .NET Compact
Framework 2.0. The target OS is Windows Mobile 5.0. I have been testing
on different (Mobile 5) devices and emulators.


Has anybody experienced something like that before? What could be the
source of such erroneous application behaviour? Right now I don't have
the slightest idea where to start searching for answers...

Any help is much appreciated.


Thanks,

Volker Lehmann

Hi lehman,

I experienced the similar kind with .net 2003 CF1.1 application ,but with
tab control with tabstops were not properly ordered (like if we design as
abcd, at runtime they will be adcb etc..) at runtime.The only solution I
know with this is int the Forms initialize component method, you have to
manually modify the values to the controls.

I too experienced the following error condition. But don;t know how to deal
with it.
"The remote connection to the device has been lost. Please verify the
device connection and restart debugging."



"Volker Lehmann" wrote:

> Hello,
>
> I am encountering strange problems in my current CF forms application.
>
>
> Sometimes controls will be rendered incorrectly, e.g. a label being
> rendered like a button - with a black border and a white background that
> changes to black when clicked with the pen and changes back to white
> afterwards. Once or twice the form itself showed the same behaviour.
>
> At other times events simply won't be handled. For example, clicking on
> the second tab of a tab control will highlight the selected tab as it
> should, but the first tab will still be shown. Or buttons and menu
> entries can be clicked (the controls do display the click event), but
> the handlers won't be called...
>
> Those problems do not occur on every form nor do they show on a given
> form every time the form is displayed. So one form may work correctly
> one time, but after restarting the application the very same form could
> cause one of the mentioned problems.
>
>
> The system does not show any error messages. Either the controls will no
> longer handle any events, or the application exits without an error. In
> that case Visual Studio shows the following message (even during tests
> on an emulator):
>
> "The remote connection to the device has been lost. Please verify the
> device connection and restart debugging."
>
> I am using Visual Studio 2005 Professional Edition and the .NET Compact
> Framework 2.0. The target OS is Windows Mobile 5.0. I have been testing
> on different (Mobile 5) devices and emulators.
>
>
> Has anybody experienced something like that before? What could be the
> source of such erroneous application behaviour? Right now I don't have
> the slightest idea where to start searching for answers...
>
> Any help is much appreciated.
>
>
> Thanks,
>
> Volker Lehmann
>