Association set error.

[guest]

At the end of the WPI install of 1.01 over 1.0 it asked if I wanted to set Lucide as the default PDF viewer. I said yes. Now the default PDF viewer is the E.exe text editor and the .pdf files are called txt files. The context menu under "open as" has "Text editor" as the only entry.

PLEASE Fix as this has really messed things up for me. Thanks. Assoedit doesn't work to fix it either.

[guest]

I found that the problem was that the Lucide object did not have *.pdf listed under Current Names on the Association tab(page 3) of the properties. Apparently the install procedure missed this during object creation so the files defaulted to txt type. Also there was no file Type listed on the Association page.

[ktk]

Please crosscheck that and fix if necessary

[dmik]

Is it still relevant? For me, both the existing installation in eComStation, the update installation and the new installation after uninstalling work as expected.

[pirx]

Version 1.30 did exactly the same on my system. Had to set all association again.

[dmik]

Perhaps, something's wrong with your system. I can not reproduce it locally. Right after installation, the Current Names tab contains here:

*.DJVU
*.PDF

and if I click on an associated file, I see Lucide as the first entry in Open As.

Please try to uninstall Lucide, cleanup your INI files (using checkini.exe from the wptools package for example) and install Lucide again.

[pirx]

Had nothing to do with my INI files. A quick look at "lucide_wpi.wis":

89	ans = WirexxShowMessage(WirexxGetEnv('title'),'Make Lucide the default program for PDF files?',4)
90	If ans = 6 Then Do
91	 /* clear any previous associations */
92	 Call SysIni 'USER','PMWP_ASSOC_FILTER','*.PDF','DELETE:'
93	 Call SysIni 'USER','PMWP_ASSOC_FILTER','*PDF','DELETE:'
94	 Call SysIni 'USER','PMWP_ASSOC_TYPE','Acrobat Document','DELETE:'
95	End

So first all associations are deleted if answered "yes". But if one then decides not to "Create Workplace Shell objects" after the installation no new associations are set. I had created my own object so this one lost its associations...

[dmik]

I would never expect that one first decides not to "Create Workplace Shell objects" and then complains that WPS associations don't work -- to me, it makes no sense (you either let the installer do all the job for you or do everything on your own). So thank you for pointing that out.

I will try to put a protection against this inconsistency to the WPI.

[dmik]

(In [434]) WPI: Make sure creation of WPS object cannot be canceled (to avoid WPS association inconsistency that takes place otherwise, see #128 for details). Fixes ticket:128.