Setting default appearance does not work in last versions

The PDF-XChange Viewer for End Users
+++ FREE +++

Moderators: PDF-XChange Support, Daniel - PDF-XChange, Chris - PDF-XChange, Sean - PDF-XChange, Paul - PDF-XChange, Vasyl - PDF-XChange, Ivan - Tracker Software, Stefan - PDF-XChange

impronta
User
Posts: 12
Joined: Wed Nov 19, 2008 5:51 pm

Setting default appearance does not work in last versions

Post by impronta »

Hello
As in the title, in the last versions of the viewer we cannot set current appearance as default, not anymore (for text objects, rectangles, etc.)
This useful feature worked until some release ago, i don't remember which one. I'm sure for example it works in 2.39.x vers, but it doesn't in the 2.0.41.x (or in the 2.0.40.x i think).
Please make some verifications.
Thank you.
ksudavid
User
Posts: 91
Joined: Thu Nov 20, 2008 10:39 pm

Re: Setting default appearance does not work in last versions

Post by ksudavid »

No problems here but there was one change that I had to figure out. For example, Create a text box and try to set current as default. No matter how many times the text setting will not stay.

Now there are 2 levels of Set as Default settings. The first will one set the defaults for the text box, callout, etc... itself. To set the defaults for the text properties your Right Click - Text Formatting - Set Current Text Formatting as Default. In other words the text default settings are separate from the object default settings.

David
User avatar
Bhikkhu Pesala
User
Posts: 1776
Joined: Tue May 29, 2007 9:29 am

Re: Setting default appearance does not work in last versions

Post by Bhikkhu Pesala »

The latest build is 41.5 so you seem to be some way behind.

I have no problem setting current object properties as the default.
Windows 10 Home 64-bit • AMD Ryzen 5 3400G, 8 Gb
Review: http://www.softerviews.org/PDF-XChange.html
impronta
User
Posts: 12
Joined: Wed Nov 19, 2008 5:51 pm

Re: Setting default appearance does not work in last versions

Post by impronta »

For Bhikkhu Pesala: in effect i'm using the very last version, that is the 2.0 build 41.5, that is what I wrote, 2.0.41.x

David, the problem is exactly the one you described! :D
I didn't realize the change you described and this is exactly the problem (and the solution).
I was sure it was a bug of new versions.
Thanks a lot for help :D