Question about autoscaling option.

Hi,

Can autoscaling option support anything of size more than VGA?? I have this drawing program, which is fine on the VGA screen, however, same program used on screen bigger than VGA, if not scale to the actual physical size, it will work fine. However, when I start to make it bigger, it gives a lot of problems such as the drawing was flashing (it is because of using the refresh function) and the lines are not continous even though my stylus has never left the touch screen (again work fine in VGA).

Thanks.
Best regards.
:icon_clap:

AutoScale handles different DPI (dots per inch) not different screen sizes. So it will not automatically resize your layout to a larger screen (unless the DPI is also higher).

Almost one year after, after a lot of searching i have exactly the same problem when moving from WM5 Device with 16 bit-per-pixel, 240 (w) x 320 (L) screen resolution to WM6 HP iPAQ 214 with TFT 65K color 480 x 640 pixel (VGA) screen.

The drawing is built using ImageLibEx Library with Drawer, Pen and ImageEx objects and MouseMove event. I always used Auto Scaled EXE Compilation.

Now drawing is always flashing and lines are messed up and as a result it can't work on my customer's PDA.

I tryied to compile without Auto-Scale but everything is messed up except the drawing, that works perfectly!

What should i do?

Thank you in advance.

Can you post a screen shot?

I have an iPaq 214, and I wrote ImageLibEx, and I have not found any problems like you are experiencing. If you have some code that demonstrates the problem then post it and I will try it on my 214.

Thank you for your answers.

I found a solution, maybe it's not the best way but it works.

When i initialize the objects i load a template empty image file that user draws on. Until now the image file had dimensions 240x95 and so had the image object with cStretchImage option on.

After many tests i found that keeping the form's image object's dimensions the same, the image file dimensions must be increased to 480x190.

Now it works fine, no refreshing and no messed up lines.

The only issue is that the image's file size has increased and gets more disk size on MSSQL Database, where it's updated like a BLOB. Unfortunately i can't save the image file in low-bit format.