PDF-XChange Viewer SDK for Developer's
(ActiveX and Simple DLL Versions)
Moderators:PDF-XChange Support, Daniel - PDF-XChange, Chris - PDF-XChange, Sean - PDF-XChange, Vasyl - PDF-XChange, Ivan - Tracker Software, Stefan - PDF-XChange
I just have upgraded from 2.42.3 to utmost recent version 2.42.4 and discovered that configuration files prepared for 2.42.3 are not being recognized properly by 2.42.4?
Content of particular configuration file is a customized tool bar that just contains a couple of UI items necessary for particular application.
Just by updating to 2.42.4 all customizations disappear. Does this mean that any "prepared" customizations have to be redone with any new version? In a different topic I just have learned that obviously some new properties (for shortcuts) have been introduced...
What is the desired behaviour? I would expect that files from previous versions are incorporated if necessary ... it seems that I have to redo all the work including testing, which is quite time consuming...
Here it is ... I have tried to load the file with the PDF-XChange Viewer Control Demo that comes along with full 2.0.42.4 SDK - the file as attached has been created with the same tool but from 2.0.42.3 ... I hope that helps you in identifying possible root cause
Cheers,
Klaus
BTW - I am awaiting the next build as I need the UNDO operation working properly as well as some other topics from my posts
Hi,
Sorry, but we cannot reproduce your problem here. Looks like all UI settings has been loaded fine. Can you be more specific – when you load settings you don’t get any changes in Viewer AX UI, or something else?
Hi, so the problem I had was that the UI didn't display any bars ... but as I found out right now this has nothing to do with potential incompatibilities between the builds - it had something to do with the surrounding environment which is used to run the application ... reason was that at startup time the .dat file was not in specific folder... sorry for that but digging down to root cause step by step led me into the following:
The LoadSettings interface method didn't report any problem when attempting to read an unspecified/nonexistent file ... from the documentation: "Returns S_OK if successful, or an error value otherwise ..." ... as the surrounding application didn't receive an error code the assumption is that everything is ok - in given case all settings regarding bars and menu items contained are being solely retrieved fom config file - since this was not present no bars have been visible ...
Anyhow, I think attempting to load something nonexistent should report an error? Or what is the AX component doing in such a case, simply ignore and continue with settings from elsewhere (registry, resource.dat ???) - it is crucial for the project I amdoing that I fully understand as from where potential settings are being retrieved - from other posts here I have learned about different path when AX is being deployed and used on XP and Vista (in respect to customized stamps and their resepective location)
