[M3devel] screen shots of pixmap problem
Randy Coleburn
rcoleburn at scires.com
Tue Aug 5 16:00:54 CEST 2008
Daniel:
Thanks, I will check this out today.
In my experience, the normal dpi setting on most all Windows computers
is 96 dpi. If the source is fixing it at 75 dpi, that would be a
problem.
Regards,
Randy
>>> "Daniel Alejandro Benavides D." <dabenavidesd at yahoo.es> 8/5/2008
9:02 AM >>>
Dear Randy:
Could you try to check (with cm3ide)
http://localhost:3800/public/vbtkit/src/lego/Image.i3/Raw#_DECL_ (or
just on cm3/m3-ui/vbtkit/src/lego/Image.i3 )
see that line 43 has
xres, yres: REAL := 75.0; (* in pixels per inch *)
which is set from the sourcecode (not from the runtime variables).
you can calulate with 1920x1200 screen resolution pixels per inch
first, you apply pythogorean theorem with both catets
Dp=sqrt(Wp^2+Wh^2)
Then PPI(or Pixels Per inch)=Dp/Di
where Di is the diagonal size in inches (the screen size), as Wikipedia
says:
http://en.wikipedia.org/wiki/Pixels_per_inch
In my case a SyncMaster 753DFX the PPI=96.42351792840054493 (Iguess
the monitor you have should have more, rigth?). So you should fixed if
needed the PPI rate in the source code or maybe use another variable
that has the correct value.
I hope this helps, let me know
Thanks
--- El vie, 1/8/08, Randy Coleburn <rcoleburn at scires.com> escribió:
De: Randy Coleburn <rcoleburn at scires.com>
Asunto: [M3devel] screen shots of pixmap problem
Para: m3devel at elegosoft.com
Fecha: viernes, 1 agosto, 2008 10:18
I managed to get the customer to grab a few screen images that
illustrate the pixmap problem we are having. These screen shots
supplied by the customer don't show the full extent of the pixmap
problem, but I do think they show the basic issues. Quality of the
bitmaps isn't great, but I think it illustrates the problem.
I think my whole application is fairly sophisticated in its use of
Trestle/FormsVBT. After the delivery, I'll try to provide the community
with a portfolio of pictures we can add to the web site to show the
capability of Trestle/FormsVBT.
The attached ZIP file contains the following files:
1. splash_1440.bmp = the startup splash screen bitmap viewed at
1440x900 resolution.
2. splash_1920.bmp = same bitmap as #1, but viewed at 1920x1200
resolution. It is huge compared to #1. Normally, when you increase
resolution on the same screen, the images get smaller, but this time
they get larger.
3. aoi_1440.bmp = one of the windows viewed at 1440x900 resolution.
4. aoi_1920.bmp = same window viewed at 1920x1200 resolution. Notice
that the black triangles in front of Polygon and Minutes are huge. The
text seems to be scaling fine, but the bitmaps are scaling much larger
to be out of proportion with the text. Also notice that the choice
radio buttons in the Coordinates block are enlarged out of proportion.
If you look at the numeric in the lower right corner you will notice
that the numeric text is elevated in the pixmap background rather than
centered. This is because the pixmap has been enlarged.
Hope these screen shots help illustrate the types of problems I am
having. I have another window that has a number of Boolean choice boxes
on it. When you go to 1920x1200 these boolean pixmaps get enlarged so
much that the window won't fit vertically on the screen anymore. The
OK, Close, Cancel buttons actually show off the screen, so the user
can't even complete the interaction. This same window at 1440x900 or
lower looks fine and fits on the screen with no issue.
Any insight folks can supply on how to resolve this issue would be
appreciated.
Regards,
Randy
Enviado desde Correo Yahoo! (
http://us.rd.yahoo.com/mailuk/taglines/isp/control/*http://us.rd.yahoo.com/evt=52431/*http://es.docs.yahoo.com/mail/overview/index.html
)
La bandeja de entrada más inteligente.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20080805/4f349ebe/attachment-0002.html>
More information about the M3devel
mailing list