| Groups | Blog | Home |
dotnet compact framework : Application targeting many devices and therefore screen sizes
It's basically the same problem. If you want to create a single form which
adapts to multiple screen sizes you can use the same techniques, lay out your designer for one particular layout, then handle the Resize event of the form and change your layout based on the forms size at runtime. Peter -- Peter Foot Windows Embedded MVP http://www.inthehand.com | http://www.peterfoot.net [quoted text, click to view] "Lonifasiko" <mloichate@gmail.com> wrote in message news:1129882184.186360.165150@z14g2000cwz.googlegroups.com... > Peter, I've already read many "orientation and dpi aware" kind > articles.I know in CF 1.0 the suggestion is create separate layout code > for each orientation. > > My problem is not being orientation aware, it's related to screen size. > I consider this two topics as different issues. Am I correct or is is > basically the same problem? > > Now, when building my forms in maximized mode, the size of the forms is > 240x320. My iPAQ displays the forms correctly. What about another > device that could have maybe (240x280)? Controls in the botton of the > form wouldn't be displayed I understand. > > Is there any solution to avoid this wihout having to create separate > layouts for each different device/different screen size? > > Regards. >
....also a fallback would be to show scrollbars so all content can be
viewed... ugly but functional. Cheers Daniel -- http://www.danielmoth.com/Blog/ [quoted text, click to view] "Peter Foot [MVP]" <feedback@nospam-inthehand.com> wrote in message news:%23N%23kN1i1FHA.2884@TK2MSFTNGP09.phx.gbl... > It's basically the same problem. If you want to create a single form which > adapts to multiple screen sizes you can use the same techniques, lay out > your designer for one particular layout, then handle the Resize event of > the form and change your layout based on the forms size at runtime. > > Peter > > -- > Peter Foot > Windows Embedded MVP > http://www.inthehand.com | http://www.peterfoot.net > > "Lonifasiko" <mloichate@gmail.com> wrote in message > news:1129882184.186360.165150@z14g2000cwz.googlegroups.com... >> Peter, I've already read many "orientation and dpi aware" kind >> articles.I know in CF 1.0 the suggestion is create separate layout code >> for each orientation. >> >> My problem is not being orientation aware, it's related to screen size. >> I consider this two topics as different issues. Am I correct or is is >> basically the same problem? >> >> Now, when building my forms in maximized mode, the size of the forms is >> 240x320. My iPAQ displays the forms correctly. What about another >> device that could have maybe (240x280)? Controls in the botton of the >> form wouldn't be displayed I understand. >> >> Is there any solution to avoid this wihout having to create separate >> layouts for each different device/different screen size? >> >> Regards. >> > >
I've already read many different articles about your application being
screen-orientation arare and dpi aware. You know all devices have got different screen sizes. My application should target as much devices as it could, and the application should be shown in maximized mode all the time, without letting the user do anything appart from interacting with the application. They cannot click on "Start".......you know, I'm targeting elderly people. How to control the issue of adapting the different forms and controls inside them, to these different screen sizes? Should I define the minimun screen size among all devices and adapt my application to this device. I think it's not the idea because devices with higher screen sizes would display large blank spaces on screen :-( Any help will be greatly appreciated. Thanks very much in advance.
Peter, I've already read many "orientation and dpi aware" kind
articles.I know in CF 1.0 the suggestion is create separate layout code for each orientation. My problem is not being orientation aware, it's related to screen size. I consider this two topics as different issues. Am I correct or is is basically the same problem? Now, when building my forms in maximized mode, the size of the forms is 240x320. My iPAQ displays the forms correctly. What about another device that could have maybe (240x280)? Controls in the botton of the form wouldn't be displayed I understand. Is there any solution to avoid this wihout having to create separate layouts for each different device/different screen size? Regards.
With .NETCF v1.0 you have to do a lot of work manually to layout your forms
for screen size/shape changes, see this article for details:- http://msdn.microsoft.com/library/en-us/dnppcgen/html/developing_orientation_and_resolution_aware_apps.asp With .NETCF v2.0 there is support for docking and anchoring which makes this somewhat easier. Peter -- Peter Foot Windows Embedded MVP http://www.inthehand.com | http://www.peterfoot.net [quoted text, click to view] "Lonifasiko" <mloichate@gmail.com> wrote in message news:1129878803.113246.30320@g43g2000cwa.googlegroups.com... > I've already read many different articles about your application being > screen-orientation arare and dpi aware. > > You know all devices have got different screen sizes. My application > should target as much devices as it could, and the application should > be shown in maximized mode all the time, without letting the user do > anything appart from interacting with the application. They cannot > click on "Start".......you know, I'm targeting elderly people. > > How to control the issue of adapting the different forms and controls > inside them, to these different screen sizes? Should I define the > minimun screen size among all devices and adapt my application to this > device. I think it's not the idea because devices with higher screen > sizes would display large blank spaces on screen :-( > > Any help will be greatly appreciated. > > Thanks very much in advance. >
A third approach is to generate Forms for each target resolution (there
aren't an infinite set yet) and decide at run time which to use. -Chris [quoted text, click to view] "Daniel Moth" <dmoth74@hotmail.com> wrote in message news:OAnhYtj1FHA.2932@TK2MSFTNGP10.phx.gbl... > ...also a fallback would be to show scrollbars so all content can be > viewed... ugly but functional. > > Cheers > Daniel > -- > http://www.danielmoth.com/Blog/ > > "Peter Foot [MVP]" <feedback@nospam-inthehand.com> wrote in message > news:%23N%23kN1i1FHA.2884@TK2MSFTNGP09.phx.gbl... >> It's basically the same problem. If you want to create a single form >> which adapts to multiple screen sizes you can use the same techniques, >> lay out your designer for one particular layout, then handle the Resize >> event of the form and change your layout based on the forms size at >> runtime. >> >> Peter >> >> -- >> Peter Foot >> Windows Embedded MVP >> http://www.inthehand.com | http://www.peterfoot.net >> >> "Lonifasiko" <mloichate@gmail.com> wrote in message >> news:1129882184.186360.165150@z14g2000cwz.googlegroups.com... >>> Peter, I've already read many "orientation and dpi aware" kind >>> articles.I know in CF 1.0 the suggestion is create separate layout code >>> for each orientation. >>> >>> My problem is not being orientation aware, it's related to screen size. >>> I consider this two topics as different issues. Am I correct or is is >>> basically the same problem? >>> >>> Now, when building my forms in maximized mode, the size of the forms is >>> 240x320. My iPAQ displays the forms correctly. What about another >>> device that could have maybe (240x280)? Controls in the botton of the >>> form wouldn't be displayed I understand. >>> >>> Is there any solution to avoid this wihout having to create separate >>> layouts for each different device/different screen size? >>> >>> Regards. >>> >> >> > >
Be careful when using that approach on device's that support rotation...
it's easy to forget to transfer some important state information from one form to another when you swap them during rotation. -- -Robert Levy Program Manager, Windows Mobile Developer Experience http://blogs.msdn.com/windowsmobile [quoted text, click to view] "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message news:One1wCk1FHA.3856@tk2msftngp13.phx.gbl... >A third approach is to generate Forms for each target resolution (there >aren't an infinite set yet) and decide at run time which to use. > > -Chris > > > "Daniel Moth" <dmoth74@hotmail.com> wrote in message > news:OAnhYtj1FHA.2932@TK2MSFTNGP10.phx.gbl... >> ...also a fallback would be to show scrollbars so all content can be >> viewed... ugly but functional. >> >> Cheers >> Daniel >> -- >> http://www.danielmoth.com/Blog/ >> >> "Peter Foot [MVP]" <feedback@nospam-inthehand.com> wrote in message >> news:%23N%23kN1i1FHA.2884@TK2MSFTNGP09.phx.gbl... >>> It's basically the same problem. If you want to create a single form >>> which adapts to multiple screen sizes you can use the same techniques, >>> lay out your designer for one particular layout, then handle the Resize >>> event of the form and change your layout based on the forms size at >>> runtime. >>> >>> Peter >>> >>> -- >>> Peter Foot >>> Windows Embedded MVP >>> http://www.inthehand.com | http://www.peterfoot.net >>> >>> "Lonifasiko" <mloichate@gmail.com> wrote in message >>> news:1129882184.186360.165150@z14g2000cwz.googlegroups.com... >>>> Peter, I've already read many "orientation and dpi aware" kind >>>> articles.I know in CF 1.0 the suggestion is create separate layout code >>>> for each orientation. >>>> >>>> My problem is not being orientation aware, it's related to screen size. >>>> I consider this two topics as different issues. Am I correct or is is >>>> basically the same problem? >>>> >>>> Now, when building my forms in maximized mode, the size of the forms is >>>> 240x320. My iPAQ displays the forms correctly. What about another >>>> device that could have maybe (240x280)? Controls in the botton of the >>>> form wouldn't be displayed I understand. >>>> >>>> Is there any solution to avoid this wihout having to create separate >>>> layouts for each different device/different screen size? >>>> >>>> Regards. >>>> >>> >>> >> >> > >
In CFv1, this happens automatically for you. In CFv2, it also happens
automatically but you can turn it off with the AutoScroll property or make it less ugly with the AutoScrollMargin property. -- -Robert Levy Program Manager, Windows Mobile Developer Experience http://blogs.msdn.com/windowsmobile [quoted text, click to view] "Daniel Moth" <dmoth74@hotmail.com> wrote in message news:OAnhYtj1FHA.2932@TK2MSFTNGP10.phx.gbl... > ...also a fallback would be to show scrollbars so all content can be > viewed... ugly but functional. > > Cheers > Daniel > -- > http://www.danielmoth.com/Blog/ > > "Peter Foot [MVP]" <feedback@nospam-inthehand.com> wrote in message > news:%23N%23kN1i1FHA.2884@TK2MSFTNGP09.phx.gbl... >> It's basically the same problem. If you want to create a single form >> which adapts to multiple screen sizes you can use the same techniques, >> lay out your designer for one particular layout, then handle the Resize >> event of the form and change your layout based on the forms size at >> runtime. >> >> Peter >> >> -- >> Peter Foot >> Windows Embedded MVP >> http://www.inthehand.com | http://www.peterfoot.net >> >> "Lonifasiko" <mloichate@gmail.com> wrote in message >> news:1129882184.186360.165150@z14g2000cwz.googlegroups.com... >>> Peter, I've already read many "orientation and dpi aware" kind >>> articles.I know in CF 1.0 the suggestion is create separate layout code >>> for each orientation. >>> >>> My problem is not being orientation aware, it's related to screen size. >>> I consider this two topics as different issues. Am I correct or is is >>> basically the same problem? >>> >>> Now, when building my forms in maximized mode, the size of the forms is >>> 240x320. My iPAQ displays the forms correctly. What about another >>> device that could have maybe (240x280)? Controls in the botton of the >>> form wouldn't be displayed I understand. >>> >>> Is there any solution to avoid this wihout having to create separate >>> layouts for each different device/different screen size? >>> >>> Regards. >>> >> >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |