@FreelanceReinh, thank you for the detailed response. I love your examples, they are quite straight-forward for me, I think I know a little for the non-proportional font now. ... View more

Or, you can use the VECTOR statement in SGPLOT procedure.   https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/grstatproc/p1wtsx90517bf4n12fpaaeh6za0l.htm ... View more

Check INTERVALBARWIDTH= option if your xaxis or yaxis is linear type: https://communities.sas.com/t5/Graphics-Programming/barwidth-has-no-effect-when-using-HIGHLOW-in-PROC-SGPLOT/m-p/939057#M24902 Chekc option lowlabel= of highlow to display a string at left side of highlow. ... View more

Hi,my friends:     when i rerun your code,in the data anno3 and forest3 steps,add the code 'if row>37 then delete in both two data step'  ,then the output forest plot appear abnormal ,two long blank will display in the bottow of the forest,wheather you and others had found the same ?   ... View more

So brilliant and simple. Thank you! ... View more

@DanH_sas wrote: Just to make sure this is an "apples-to-apples" comparison, can you generate the output using the WORD destination and set the OUTPUTFMT on the ODS GRAPHICS statement to be SVG? The default DPI for PDF output is 150dpi, whereas WORD is using either 96 or 100dpi. That might be causing variation. Hi Dan.  I tried with the Word destination; however, I got the following warnings.   WARNING: The ODS WORD destination is preproduction in this release. WARNING: Word destination does not support SVG images. Using the default static format. The same difference in font size occurs between gTitle and noGTitle.  That's seen in [test side-by-side Word destination.docx].  Is there another outputFmt you would suggest to try rather than the default static format?   Edit: I tried EMF, and that seems to have fixed the issue.  Now, the comparison looks more or less the same size, just with different smoothing.  That's the [test side-by-side Word EMF.docx] attachment. ... View more

Historical reasons is quite likely. SAS actually does a fair amount of work to make sure that code that worked in a previous version still "works" though some minor behaviors may change. You may get notes or warnings depending on specific code about some of these option.   For example some documentation directly related to your question (from my 9.4.7 online help): CATEGORY=column | expression specifies the column or expression for the category values. Notes You can use X= as an alternative to CATEGORY=. If you use X=, then be aware that the TIP=, TIPFORMAT=, and TIPLABEL= options recognize X as the category role and not as CATEGORY.   This tells me that if I were using the Tip, Tipformat or Tiblabel options then use of X= instead of Category= may yield some difference in output.   You will see in procedures places where you can specify an option with "alias" names. Sometimes these reflect an earlier version of the options for a procedure that has evolved.   ... View more

> So now if I decide that 'ginormous' is unprofessional, and I want to change that format label to '2xl', I've got to remember to change the description both in the format and in the dattrmap dset. I think it'd be much cleaner if I could just set the value var to the exact type & domain as the grouping var.   Right, which is why I prefer to use the formatted values in the dattrmap and in PROC SGPLOT, rather than the unformatted values. In your example, define the format FIRST, then define the dattrmap by specifying the raw values (4,5,6,8,10) and using the PUT function to apply your format. That defines the dattrmap in terms of the formatted values. In PROC SGPLOT, apply the format to the cylinders variable.   For a recent example, see this thread, which also include links to blog articles: https://communities.sas.com/t5/SAS-Programming/Bar-Chart-Axis-Parameters-and-Color-Scaling/m-p/917634#M361459   You can also use programming to automatically generate the dattrmap from the data and the format  but sometimes that is overkill. Use the simpler method when you can. ... View more

After further investigation, the effective minimum size for the arrowhead on the series plot cannot be smaller than 8 pixels. ... View more

FYI...BACKLIGHT option is available on TEXT plot for such use cases.  The label will be back lit with a contrasting color so the label will show up even if the bar and text colors match.  This could simplify the solution. ... View more

I've done something similar to this with band plot. Take a look at page 2 of https://support.sas.com/resources/papers/proceedings09/324-2009.pdf   Hope this helps! Dan ... View more

Hi Jay, thank you very much! I spent so much time following another tutorial but didn't work out for me, and your answer helped me out right away! ... View more

@Jay54  Very easy and efficient method, thankyou ... View more

Thank u I also forwarded to other authors ... View more

@JeffMeyers The problem is little bit different now. I have used the format as eval(put(ifn(paramcd="MDS", avisitn,.),vs.)). I have now used type=linear for xaxisopts as the visit numbers are not equidistant.  However, I got warning as: WARNING: SCATTERPLOT statement has a conflict with the axis type. The plot will not be drawn. WARNING: SERIESPLOT statement has a conflict with the axis type. The plot will not be drawn. I think linear axis option is not compatible with put fuction due to conversion to character format. Is there any way to solve this? The format "vs" is defined as: proc format; value vs 2="Pre-D0" 3="Post-D0" 6="Pre-W3" 7="Post-W3" ; run; ... View more