search

ccgreen13 / grafx2

Automatically exported from code.google.com/p/grafx2
0 stars 0 forks source link

Legacy: setting "Auto set resolution" #25

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
The usability of this feature is questionable.
The idea was that if you opened a 320x400 image, it would auto-select the 
according Mode-X which has the very "flat" pixels.

I don't recommend for any user to activate this feature, because nowadays 
we have no platform that provides such modes.
My laptop LCD, on linux, is the only one that accepted all the default 
GrafX2 "resolutions". I configured it to not stretch images, so it centers 
the area and displays black borders, doubling pixels when possible. All 
modes look good but in all cases the pixels are square and I have no 
reason to choose a smaller drawing area, so no reason to let GrafX2 choose 
depending on picture size. I'd rather choose manually one of the two 
fullscreen modes hi-res 1024x768 and low-res (very pretty!) 512x384.

Affects: settings screen "Auto-set res"
INI: Auto_set_resolution
INI: Set_resolution_according_to

Original issue reported on code.google.com by yrizoud on 7 Oct 2008 at 9:55

GoogleCodeExporter commented 9 years ago 
Set to low (All the 'Legacy' are reminders of things that might be removed)

Original comment by yrizoud on 7 Oct 2008 at 10:09

GoogleCodeExporter commented 9 years ago 
I plan to add some modes with rectangles pixels for Amstrad CPC graphists. this
computers has strange screenmodes with 2:1 or 1:2 aspect ratio. Don't know if 
this
option will be usefull, but it may be handy to have it around ...

The idea is to have a X and a Y zoom factor for the picture even in non-zoomed 
mode.
Some people also requested to have a zoom like that for LCD that can't stretch 
the
picture.

Original comment by pulkoma...@gmail.com on 7 Oct 2008 at 11:26

GoogleCodeExporter commented 9 years ago

Original comment by pulkoma...@gmail.com on 7 Oct 2008 at 2:54

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago

Original comment by pulkoma...@gmail.com on 24 Dec 2008 at 4:15

GoogleCodeExporter commented 9 years ago

Original comment by pulkoma...@gmail.com on 14 Jan 2009 at 4:44

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
This setting could be used to scale the window up when loading a picture.

Original comment by pulkoma...@gmail.com on 23 Feb 2009 at 6:10

GoogleCodeExporter commented 9 years ago 
I agree that this feature is of very limited usability (since you can always 
just
change the resolution yourself). But you can still use any resolution you want 
even
on a modern computer (at least if it's running Linux and you have a working 
driver).
And if all the resolutions you use have the same frequency you smoothly and 
instantly
change between them without flicker (which hasn't always been possible). So this
feature is at least as useful now as it has ever been.

Here is how you use 320x400 at, let's say, 80Hz in X (XFree86 or Xorg on any
platform). Add the following line to the monitor section:

Modeline "320x400" 14.83 320 352 408 440 400 407 413 421

And to test it without restarting X you can run:

xinit /path/to/grafx2 -- /usr/bin/X :1

In fact this resolution will work better than 320x200 in most cases since some 
newer
graphic interfaces can't do doublescan (draw each line twice to avoid so called
scanlines) and using it without doublescan will either result in a horizontal 
sync
frequency too low or a refresh rate too high for most monitors to handle (as 
well as
scanlines of course).

Original comment by magnu...@algonet.se on 1 Mar 2009 at 11:11

GoogleCodeExporter commented 9 years ago

Original comment by pulkoma...@gmail.com on 26 May 2009 at 7:48

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago

Original comment by pulkoma...@gmail.com on 15 Sep 2009 at 7:13

GoogleCodeExporter commented 9 years ago

Original comment by pulkoma...@gmail.com on 15 Jan 2010 at 7:34

GoogleCodeExporter commented 9 years ago

Original comment by pulkoma...@gmail.com on 10 Apr 2011 at 8:43

GoogleCodeExporter commented 9 years ago 
Arbitering issues that make it to v2.4

Original comment by yrizoud on 8 Mar 2012 at 7:18