topic Re: SASHELP.VGOPT vs PROC GOPTIONS in Graphics Programming

SASHELP.VGOPT vs PROC GOPTIONS

ArtC — Thu, 18 Nov 2010 07:46:57 GMT

Can anyone tell me why sashelp.vgopt and PROC GOPTIONS do not necessarily yield the same result? (SAS9.2 under Windows)

[pre]goptions reset=all dev=win;
proc goptions option=hpos;
run;
proc print data=sashelp.vgopt(where=(optname='HPOS'));
var optname setting;
run;
[/pre]
This is just one option that is different. There are others. The SASHELP.VGOPT view seems to have the correct values.

Re: SASHELP.VGOPT vs PROC GOPTIONS

Ksharp — Fri, 19 Nov 2010 05:41:43 GMT

Hi.Art Carpenter.
Perhaps you need to talk to Technical Group.
I also think these both are identical.

Regards.

Ksharp

Re: SASHELP.VGOPT vs PROC GOPTIONS

data_null__ — Fri, 19 Nov 2010 13:52:29 GMT

Not WHY but it appears the dictionary or view is looking at the driver info LROWS and LCOLS.

[pre]
GDEVICE procedure
Listing from SASHELP.DEVICES - Entry WIN

Orig Driver: WIN Module: SASGDDMX Model: 26001
Description: Microsoft Windows Display Type: CRT
*** Institute-supplied ***
Lrows: 10 Xmax: 15.000 IN Hsize: 0.000 IN Xpixels: 1280
Lcols: 35 Ymax: 12.000 IN Vsize: 0.000 IN Ypixels: 1024
Prows: 0 Horigin: 0.000 IN
Pcols: 0 Vorigin: 0.000 IN

[/pre]

Re: SASHELP.VGOPT vs PROC GOPTIONS

Andre — Fri, 19 Nov 2010 14:31:07 GMT

Art

With the old manner
[pre]
proc gdevice catalog=sashelp.devices browse nofs;
list win ;
quit;
[/pre]

or with this
[pre]
proc goptions short;run;
[/pre]

you have it , but not alone !

Andre 😉