[Radiance-dev] Re: Re: Rvu window? (moved from Radiance-dev)

Carsten Bauer wrote:

If you simply set the window sizes in pixels, and the ratio doesn't
match the angle aspect ratio, you'll end up with a window filled only
partially by the image in one dimension, which doesn't look very
professional.

Rpict treats -x and -y as maximum values. If the opening angles
result in a different image aspect, then it will fit the largest
possible rectangle of that aspect within the given -x/-y hull.

Rview applies the same concept, but uses the screen size as the hull.
It would be simple and straightforward to allow for a -geometry
override to that if someone is willing to volunteer the necessary
changes.

At the same time, it would probably be confusing to have -x and
-y determine the window size, because in a preview we usually
want to see a as much as possible as fast as possible. With rpict
we rather want (more) accurate results and may determine the
picture size based on the time we're willing to wait for them.

-schorsch

···

--
Georg Mischler -- simulations developer -- schorsch at schorsch com
+schorsch.com+ -- lighting design tools -- http://www.schorsch.com/

The original question remains. Where do the defaults live? This discussion has moved toward reinventing the wheel, if you ask me. My question in July was how does one control default window sizes in X. Marija may be looking to specifically override the defaults with rvu (that does seem to be the question there), but the fact remains, if we can determine where the defaults are stored for some of our common Xen, that may be the simpest way. (?)

···

-------------------
    Rob Guglielmetti
www.rumblestrip.org

Georg Mischler wrote:

At the same time, it would probably be confusing to have -x and
-y determine the window size, because in a preview we usually
want to see a as much as possible as fast as possible. With rpict
we rather want (more) accurate results and may determine the
picture size based on the time we're willing to wait for them.

OK, for a preview image the exact pixel size is probably not really important, as long as it is fast and looks good ..

A rest of confusion, however, will always remain, because either in rpict or with a new X-Style geometry specification to rvu, with the currently employed hull principle one value will be usually overridden (as long as you don't have a table of the tangent function ready when typing in the values..), and you're not even shure which one, x or y.

BTW: again only a handful of dudes is discussing this, and the millions or billions of Radiance users in the whole wide world remain silent :slight_smile: Now, come on, let us hear your voice, you had a decent opinion recently on Bush vs. Kerry, what about angles vs pixels ???

-cb

Rob Guglielmetti wrote:

The original question remains. Where do the defaults live? This discussion has moved toward reinventing the wheel, if you ask me. My question in July was how does one control default window sizes in X. Marija may be looking to specifically override the defaults with rvu (that does seem to be the question there), but the fact remains, if we can determine where the defaults are stored for some of our common Xen, that may be the simpest way. (?)

,

two more bits to add:

man xrdb says:

       Xrdb is used to get or set the contents of the RESOURCE_MANAGER property on the root window of screen 0, or the SCREEN_RESOURCES property on
       the root window of any or all screens, or everything combined. You would normally run this program from your X startup file.

       Most X clients use the RESOURCE_MANAGER and SCREEN_RESOURCES properties to get user preferences about color, fonts, and so on for applica-
       tions. Having this information in the server (where it is available to all clients) instead of on disk, solves the problem in previous ver-
       sions of X that required you to maintain defaults files on every machine that you might use. It also allows for dynamic changing of defaults
       without editing files.

so, sticking to the X WIndow System standards, one would put lines like

    radiance.rvu.x:800
    radiance.rvu.y:600

in a file and read that at start up of X. (xrdb -merge .Xdefaults would be typically used in a .xinitrc file at startup)

Concerning overriding the aspect ratio given in the view with that of pixel dimensions: rshow had (and has) the same problem and being able to select the behaviour is nice. To avoid yet another cmdline option in rvu, setting one pixel dimension would set the other pixel dimension from the aspect ratio given in the view file, whereas two user supplied pixel dimensions will fix the view aspect ratio. That'll be backward compatible too.

-Peter

···

--
pab-opto, Freiburg, Germany, http://www.pab-opto.de
[see web page to check digital email signature]