Opened 13 years ago

Closed 10 years ago

#128 closed defect (fixed)

Association set error.

Reported by: guest Owned by: ktk
Priority: minor Milestone: 1.3.2
Component: Plugin: PDF Version:
Keywords: Cc:

Description

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.

Change History (9)

comment:1 Changed 13 years ago by 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.

comment:2 Changed 12 years ago by ktk

Component: Lucide CorePlugin: PDF
Milestone: 1.2
Owner: changed from Eugene Romanenko to ktk
Priority: majorcritical
Status: newassigned
Version: 1.0 Beta 3

Please crosscheck that and fix if necessary

comment:3 Changed 10 years ago by 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.

comment:4 Changed 10 years ago by pirx

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

comment:5 Changed 10 years ago by 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.

comment:6 Changed 10 years ago by dmik

Priority: criticalminor

comment:7 Changed 10 years ago by 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...

comment:8 Changed 10 years ago by 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.

comment:9 Changed 10 years ago by dmik

Resolution: fixed
Status: assignedclosed

(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.

Note: See TracTickets for help on using tickets.