Loading Profile...
Problem with "Fill Screen" preference
With the new version of Hyperspaces (including the preferences for Growl),
I noticed a slight modification of the "Fill Screen" effect for my background images that looks like a bug?
If I have a laaaarge horizontal image (let's say a 16:9 picture) to be displayed on a monitor with a different ratio (let's say a 4:3 monitor):
BEFORE, the "Fill Screen" option would make my picture be visible on the whole desktop, as we can deduce from the name of this option.
NOW, the same "Fill Screen" option with the same 16:9 picture, makes it fit to the right and left side, with a "letter box" effect... That is to say with empty areas at the top and at the bottom of the display.
I can switch to the option "Stretch to fill screen" to get display on my whole desktop, but:
- this is not intended to be the same effect (No visual deformation with "Fill Screen")
- and... before this was working ;-)
P.S. This is a sort of exchange between "Fit to screen" and "Fill screen" in this case.
P.S.2 The reverse configuration, i.e. 4:3 picture on a widescreen display is perfectly working.
P.S.3 Using a picture with a "vertical ratio" (i.e. height > width) shows the same bug (sort of exchange of "Fill Screen" and "Fit to screen").
I noticed a slight modification of the "Fill Screen" effect for my background images that looks like a bug?
If I have a laaaarge horizontal image (let's say a 16:9 picture) to be displayed on a monitor with a different ratio (let's say a 4:3 monitor):
BEFORE, the "Fill Screen" option would make my picture be visible on the whole desktop, as we can deduce from the name of this option.
NOW, the same "Fill Screen" option with the same 16:9 picture, makes it fit to the right and left side, with a "letter box" effect... That is to say with empty areas at the top and at the bottom of the display.
I can switch to the option "Stretch to fill screen" to get display on my whole desktop, but:
- this is not intended to be the same effect (No visual deformation with "Fill Screen")
- and... before this was working ;-)
P.S. This is a sort of exchange between "Fit to screen" and "Fill screen" in this case.
P.S.2 The reverse configuration, i.e. 4:3 picture on a widescreen display is perfectly working.
P.S.3 Using a picture with a "vertical ratio" (i.e. height > width) shows the same bug (sort of exchange of "Fill Screen" and "Fit to screen").
I’m confident
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solution from the company
-
Hi RYann, could you please download this newer test build and see if it behaves the way you expect with respect to the image scaling settings?
http://hyperspacesapp.com/nightly.zip
I’m confident
The company says
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi RYann, you're right - Fit to screen and Fill screen appear to be reversed in this build. I'm not going to try to fix this tonight - my brain is mush at this point - but I will tomorrow.
I’m also confident
-
Inappropriate?Hi RYann, could you please download this newer test build and see if it behaves the way you expect with respect to the image scaling settings?
http://hyperspacesapp.com/nightly.zip
I’m confident
The company says
this solves the problem
-
Inappropriate?Wouah, how fast!
My answer is "yes and no".
Yes it solves some problems.
Yes (BTW) it solves another bug I noticed: the drag'n'drop of images to the Preference pane.
But no, it's not totally solved :
=> For instance, the following image attached to this message has "vertical" dimensions (height > width) and, from my point of view, has a bad behavior with the option "Fill Screen" since only half the screen is filled and its center is strangley placed.
As far as I understand this "Fill Screen" option, this should fill the whole current display, by zooming or unzooming the image to the best fitted factor, but without visual deformation (keep the aspect ratio) :
a sort of "Fit to screen", but instead of making the larger dimension fit to the screen (and resulting in empty vertical or horizontal bands), this option would make the smaller dimension fit to the screen (and resulting in hidden vertical or horizontal bands).
Am I wrong?
I’m confident
1 Comment Add a comment
This solves the problem
-
Have you tried this with a few different images of similar proportions? There appears to be something a little wrong with this image on my set-up, where other more extremely shaped images work (I have some wonderful test cases for this one!). I wonder if the image might be slightly corrupt? -
Inappropriate?Because of your answer, I tried a lot of pictures... and the situation is even weird :-(
- for "small" image, it seems to behave as I think it would (small means image smaller than the display)
- but for many other images, bigger than my display, I have so different results (and often surprising) that I'm no longer sure of the meaning of each option.
As far as I understand:
1) "Fit to Screen" should never truncate anything of an image, BUT you can get empty bands (horizontal or vertical depending on the ratio) to fill the screen?
=> Nevertheless, I got some pictures where the upper and lower bands were not visible.
2) "Fill Screen" should, on the opposite, adapt the smaller dimension of the image to the display, and therefore some bands of the image would be invisible?
=> As mentioned above, I have some images where it oesn't work.
3) "Stretch to fill Screen" seems to be OK each time for me: unlike the two previous transformation, this one is not supposed to keep the aspect ratio and simply fill the display with the original image.
=> it works!
4) "Center" => OK
5) "Tiled" => OK
Then before going deeper into this bug, would you be kind to
- confirm that my understanding of each option, decribed above, is correct.
- an maybe try some various "big" images on your side to maybe see some bad cases like mine?
I’m undecided
-
Inappropriate?Your descriptions of how this should behave are spot on.
I believe this problem is now fixed in 1.0 beta 6 (released tonight). Can you please try the new build, and let me know if it works? (and perhaps mark this issue as resolved if it does solve the problem).
I’m confident
EMPLOYEE
