Thanks you very much Peter. I download ran the Hx4700fix.exe so it doesn't
crash anymore. Now I just need to fix the invisible ToolBars icons using the
alternative initialization method.
"Peter Foot [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> John,
>
> It's come up a few times on the group before and at the moment the hx4700
> seems to be the only unit affected
>
http://groups.google.com/groups?hl=e...mpactframework
>
> A solution is to initialise your ImageList manually after the Initialize
> Component method and then assign it to the toolbar. There is a description
> and code sample here:-
> http://www.pc-counselor.com/hx4700.htm
>
> Peter
>
> --
> Peter Foot
> Windows Embedded MVP
> www.inthehand.com | www.opennetcf.org
>
> "John Kendrick" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> >I have and application that was developed to run on the H5550. Recently,
we
> > decided to purchase HP's latest model the Hx4700 (which is HP's
> > replacement
> > for H5550). When I run the same application on it, it throws an
exception
> > while initializing the forms. I traced the line down to when it loads
the
> > Images into the ImageList that the form's ToolBar uses.
> >
> >
this.theToolbarImageList.Images.Add(((System.Drawing.Image)(resources.GetObj
> > ect("resource"))));
> >
> > In the debugger I can view the "Images" collection and see the
> > "resources.GetObject" call returns a bitmap size 16x16. However, it
throw
> > the exception on the "Add" apparently. When viewing the Splash screen
form
> > I
> > can see that is loaded is displaying correctly (only difference is the
> > lack
> > of ToolBar on it).
> >
> > One theory on working on is some incompatibility in the DPI. The old
> > device
> > used 96 while the new device uses 192. I cannot give an more information
> > on
> > the Exception because even in the debugger it is reported as a
> > System.Exception with no addition information.
> >
> > Has anyone else run into problems maintaining application compatibility
> > between PPC2003 and Windows Mobile 2003 Second Edition or thoughts on
> > debugging the problem?
> >
> >
>
>