Hi Rahul;

   This is not a bug!

   I thought that this was a bug too when I initially saw this during beta testing but was informed by Engineering that this is the default reporting state that PB 12.6 used when you return to the DW Painter. The DW painter always shows you the XML Setting first. You can see the actual PDF setting if you reselect the PDF state from the Format to Configure dropdown setting in the properties pane. Then the DW Painter will then show you the actual rendering method in effect.

 The actual NativePDF! setting is adhered to internally within the DWO source code.   So another way to verify your PDF settings is to look in the DWO source code for the  "Method=n" setting. You can see this and also verify your PDF settings by editing the DWO source code, as follows:

• If the DW is using XLSFO! then the export statement will be ...

export.pdf(method=1 distill.custompostscript="0" xslfop.print="0" nativepdf.customsize=2 nativepdf.customorientation=2 )

•   If the DWO is using GhostScript (aka Distill!) then the export statement will be ...

export.pdf(method=0 distill.custompostscript="0" xslfop.print="0" nativepdf.customsize=2 nativepdf.customorientation=2 )

•  If you have chosen the NativePDF! option for data export, then the export statement will be ...

export.pdf(method=2 distill.custompostscript="0" xslfop.print="0" nativepdf.customsize=2 nativepdf.customorientation=2 )

    Again, the default for the DW Painter is to show you the XML property setting upon return ( which makes it confusing when you close & the re-open the DW Painter). Just remember when you return any DWO to re-select the PDF setting in the property's Data Export pane to see what the actual feature is that the DW is using for PDF processing.

HTH

Regards ... Chris