Home/ Questions/Q 630767
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T19:53:29+00:00

Situation A Flex project exported as a Projector, showing fullscreen. The project has a

  • 0

Situation
A Flex project exported as a Projector, showing fullscreen. The project has a background and several dots which each represent a “Location”. These locations are fetched from an XML file and have their position set in percentages. The location in pixels is calculated (this works as it should) by the width and height of the Application. The dots are placed correctly.

The background is a JPG with a resolution of 1280*1024. At this moment, the background is set on a Canvas with backgroundSize = auto. This places the image in the center without stretching it. Stretching results in ugly, pixelated images and tears the proportions apart.

Problem
When we view the project on 2 different resolutions (1 = 1280*1024; 2 = 1024*768), the dots are in the good position, the background image is sharp. But – because of the background having the same resolution as 1, the background isn’t fully shown in resolution 2 (because it isn’t stretched. A logic result.

That’s why I tried stretching the background. The results:
Dots placed in the correct way http://i733.photobucket.com/albums/ww336/winkelman66/example1.jpg

On a smaller/other resolution:
alt text http://i733.photobucket.com/albums/ww336/winkelman66/example2.jpg

Solution?
How should I solve this problem? I thought of always having the background centered on the bottom, leaving the proportions as they are. This is not an option because of missing details/parts of the image. Stretching results in ugly, pixelated images which are out of proportion.
I know stretching might be the only option to tackle the resolution problem without losing parts of the image, but how can I solve the problem where the dots aren’t in the good position (like image 2 shows).

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Big problem, simple solution (after working hours on this).
    We just forgot 1 simple thing in our calculations: reflect the size (width/height) of the dots in the position…

    So if you face the same problem when calculating the location in pixels from percentages, don’t forget to include (viewToBePositioned.width / 2) in your calculations 🙂

    • 0