Upgrading to the .323.2 SDK for Tracker Xchange. We are experiencing an issue when trying to parse the new *.xces settings file with the library that we have used up to .322.7 for *.xcs. The code we had used is, specifically "op.settings.import":
"
Dim op = pdfCtrl.Inst.CreateOp(pdfCtrl.Inst.Str2ID("op.settings.import"))
If File.Exists(sFilePath) Then
op.Params.Root("Input").v = fsInst.DefaultFileSys.StringToName(sFilePath)
op.[Do]()
End If
"
Is there a new library equivalent that we need? What we are trying to do is export the XCS and import as XCES. Alternately is there a way to convert from XCS to XCES?
Any help would be appreciated .
Doc.It Development
*.xces settings file issue
Moderators: TrackerSupp-Daniel, Tracker Support, Paul - Tracker Supp, Vasyl-Tracker Dev Team, Chris - Tracker Supp, Sean - Tracker, Ivan - Tracker Software, Tracker Supp-Stefan
Forum rules
DO NOT post your license/serial key, or your activation code - these forums, and all posts within, are public and we will be forced to immediately deactivate your license.
When experiencing some errors, use the IAUX_Inst::FormatHRESULT method to see their description and include it in your post along with the error code.
DO NOT post your license/serial key, or your activation code - these forums, and all posts within, are public and we will be forced to immediately deactivate your license.
When experiencing some errors, use the IAUX_Inst::FormatHRESULT method to see their description and include it in your post along with the error code.
- Patrick-Tracker Supp
- Site Admin
- Posts: 1645
- Joined: Thu Mar 27, 2014 6:14 pm
- Location: Vancouver Island
- Contact:
Re: *.xces settings file issue
Hello docu-track99,
You have posted this in the End-user forums. I have moved this topic to the Editor SDK forums. In order to ensure a speedy reply, please take care, in the future, to post your questions in the appropriate forums: viewforum.php?f=66
You will not get a response from our dev team by posting in the end user forums.
Thank you for your cooperation and understanding.
You have posted this in the End-user forums. I have moved this topic to the Editor SDK forums. In order to ensure a speedy reply, please take care, in the future, to post your questions in the appropriate forums: viewforum.php?f=66
You will not get a response from our dev team by posting in the end user forums.
Thank you for your cooperation and understanding.
If posting files to this forum, you must archive the files to a ZIP, RAR or 7z file or they will not be uploaded.
Thank you.
Cheers,
Patrick Charest
Tracker Support North America
Thank you.
Cheers,
Patrick Charest
Tracker Support North America
-
- User
- Posts: 5522
- Joined: Fri Nov 21, 2014 8:27 am
- Contact:
Re: *.xces settings file issue
Hello docu-track99,
Please give us a sample files that we can recreate the issue with.
Cheers,
Alex
Please give us a sample files that we can recreate the issue with.
Cheers,
Alex
Subscribe at:
https://www.youtube.com/channel/UC-TwAMNi1haxJ1FX3LvB4CQ
https://www.youtube.com/channel/UC-TwAMNi1haxJ1FX3LvB4CQ
-
- User
- Posts: 518
- Joined: Thu Dec 06, 2007 8:13 pm
Re: *.xces settings file issue
Hello Support,
We have followed the same upgrade path as we had in the past. Namely from .318 to .322.7. The configuration file was DefaultViewerSettings.xcs for 322.7. We had used the code pasted in the original message to parse the *.xcs file. As we are trying to update to 323.2 the code no longer works since the extension changed to *.xces. We either need a new library (as opposed to "op.settings.import", or we need some way to convert *.xcs to *.xces. Basically we need 323.2 working with our current shell and a way to parse the new settings format.
Thank you for your patience
We have followed the same upgrade path as we had in the past. Namely from .318 to .322.7. The configuration file was DefaultViewerSettings.xcs for 322.7. We had used the code pasted in the original message to parse the *.xcs file. As we are trying to update to 323.2 the code no longer works since the extension changed to *.xces. We either need a new library (as opposed to "op.settings.import", or we need some way to convert *.xcs to *.xces. Basically we need 323.2 working with our current shell and a way to parse the new settings format.
Thank you for your patience
- Attachments
-
- DefaultViewerSettings.zip
- (29.18 KiB) Downloaded 72 times
-
- User
- Posts: 5522
- Joined: Fri Nov 21, 2014 8:27 am
- Contact:
Re: *.xces settings file issue
Hello docu-track99,
Why are you referring to the import settings operation as to parsing?
Anyways, I've given the settings to the appropriate developer - we'll wait for his reply.
Cheers,
Alex
Why are you referring to the import settings operation as to parsing?
Anyways, I've given the settings to the appropriate developer - we'll wait for his reply.
Cheers,
Alex
Subscribe at:
https://www.youtube.com/channel/UC-TwAMNi1haxJ1FX3LvB4CQ
https://www.youtube.com/channel/UC-TwAMNi1haxJ1FX3LvB4CQ
-
- User
- Posts: 518
- Joined: Thu Dec 06, 2007 8:13 pm
Re: *.xces settings file issue
Because we save our custom settings, we therefore have to load, and parse the settings file.Sasha - Tracker Dev Team wrote:Hello docu-track99,
Why are you referring to the import settings operation as to parsing?
Thank you.Sasha - Tracker Dev Team wrote: Anyways, I've given the settings to the appropriate developer - we'll wait for his reply.
Cheers,
Alex
-
- User
- Posts: 5522
- Joined: Fri Nov 21, 2014 8:27 am
- Contact:
Re: *.xces settings file issue
Well, are you doing some custom parsing, or are you referring to parsing as to the Control reading the settings file?Because we save our custom settings, we therefore have to load, and parse the settings file.
Cheers,
Alex
Subscribe at:
https://www.youtube.com/channel/UC-TwAMNi1haxJ1FX3LvB4CQ
https://www.youtube.com/channel/UC-TwAMNi1haxJ1FX3LvB4CQ