Change Control positions and sizes after compile.

Discussion in 'Questions (Windows Mobile)' started by burd27, Dec 30, 2007.

  1. burd27

    burd27 Member Licensed User

    Hi all,

    I am writing a program that contains a lot of text boxes, combo boxes, etc. on the display. When compiled on the old v5.80 all was fine, but now when I compile it using v6.01 (Optimized), the compile process says that it is all okay, BUT, when I run it on my device (Dell Axim X51v) some of the text box sizes have changed and the entire screen contents is all over the top of each other in the top left hand corner of the screen.

    If I compile in Standard mode, all is okay (apart from loosing the advantages of v6.01 / .Net 2.0). I suspect that it may have something to do with the Axim X51v having a VGA screen that .Net 2.0 doesn't handle or that requires an extra file.

    I'm on a steep learning curve at the moment, so any help would be much appreciated.

  2. Erel

    Erel Administrator Staff Member Licensed User

    Burd, I've sent you a private message a couple of days ago.
    Please read it.

    About this problem.
    .Net 2.0 applications don't treat VGA screens like .Net 1.0 applications.
    You should change the screen to 640 * 320 in the Visual Designer to emulate a VGA screen in .Net 2.0.
  3. Filippo

    Filippo Expert Licensed User

    I have the same problem.

    Setting the screen at 640x320 is no problem, but I have 17 forms in my application and all I need now controls change in the size of a position.:sign0148:

  4. burd27

    burd27 Member Licensed User

    Tried resizing screen but that revealled more problems

    I tried resizing the screen to accommodate the VGA fo .Net2. In some respects that helped (once I resized the controls and moved them, etc.), but I am unable to make it work as there seems to be a lack of correlation between the control sizes and the font size that is set for that control.

    A good example is a Calendar box. Setting the font size to eg. 8, make the calendar date show okay, but when you drop down to reveal the month, etc., all the days are mingled in with each other as it appears to be a much larger font size. I am having similar problems with text boxes, buttons, etc.

    In addition to this, the screen layout on the desktop appears very differently on the device. Therefore the only way that I could position a control correctly (both size and position) is to compile, load to device and check. This process I have done over and over and over, until I gave up.

    Any suggestions?

  5. Erel

    Erel Administrator Staff Member Licensed User

    I suggest you to use the regular compiler instead of the optimized compiler to create the VGA application (use a regular 240 * 320 screen in the designer).
  6. Put Claude

    Put Claude Active Member Licensed User


    same resolution problem, I posted it already, so I have to stay in NET1, also for the serial troubles I have to stay in NET1... ;-)

    Put Claude Belgium
    Last edited: Jan 1, 2008
  7. burd27

    burd27 Member Licensed User

    Further observations

    Thanks Erel for your reply.

    Yes I have settled that at least for the moment .Net 1 will have to suffice....:(
    Although I was looking forward to making full use of the VGA display.

    Further to my previous post, what I have noticed (using the Calendar example again) is that when setting the font size of the Calendar Control, it would automatically set the Height of the control (width is user variable) - all this as per normal. However, on the device, when you select the Calendar so that it drops down the box showing a month at a time, the font size for the box appears too big so all the day numbers are over the top of each other, etc. This I also mentioned in my previous post, but what I have realised since then is that it is NOT that the numbers (font) are too big, but rather that the drop down box is too small to fit the numbers.

    Erel, whatever parameters you have set for the controls when automatically sizing the controls, it appears that when you make the change to the VGA screen size, only the font actually increases, but not the Control Size.

    Is this a modifiable parameter of B4P or is it tied up in .Net2?


  8. Erel

    Erel Administrator Staff Member Licensed User

    Except of the Calendar control which is a custom control everything is done by the OS.
    The Calendar is currently not applicable to VGA screens in optimized compilation.

    As I wrote in another thread, you could use .Net 2.0 but not the optimized compilation.
    You could see the Tetris example for a simple way of handling most controls with a VGA screen:
  9. Standa

    Standa Member Licensed User

    I have the same problem with calendar right now. Is planned fixed calendar for VGA devices in future versions of B4PPC?
  10. Erel

    Erel Administrator Staff Member Licensed User

    The calendar control will support VGA devices in the next release.
  11. Paulsche

    Paulsche Well-Known Member Licensed User

    Erel Hi, I have now also the Calendar VGA problem, there is already a solution?
  12. Erel

    Erel Administrator Staff Member Licensed User

    The Calendar VGA problem is fixed. The fix will be be part of the next version.
  13. Paulsche

    Paulsche Well-Known Member Licensed User

    Thanks Erel, until when you can about the next version expected?
  14. Paulsche

    Paulsche Well-Known Member Licensed User

    Erel Hi, I have the solution for my problem, Filipos fgcontrol works perfectly in VGA.

  15. Erel

    Erel Administrator Staff Member Licensed User

    The beta version should be released in a few days.
  16. Paulsche

    Paulsche Well-Known Member Licensed User

  17. Paulsche

    Paulsche Well-Known Member Licensed User

    Filipos Control works in VGA, but it is unfortunately not
    Finger-friendly, since you just click on the arrow must be at the calendar
    I'm waiting now on the update from Erel
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice