Opened 2 years ago

Closed 11 months ago

#348 closed defect (fixed)

Lucide leaves its INI file in the document directory when started from outside its own directory

Reported by: lewisr Owned by: gyoung
Priority: major Milestone: 1.4.1
Component: Backend Version: 1.4.0
Keywords: Cc:

Description

I have been wondering why I've been forced to reset my preferences so often.

I started Lucide from Directory Master, in a sparsely populated directory well outside Lucide's program location. When I exited, I had a LUCIDE.INI in the document directory.

Marking this high priority as people are bound to notice this quickly.

Change History (2)

comment:1 Changed 2 years ago by gyoung

  • Owner set to gyoung
  • Status changed from new to assigned

comment:2 Changed 11 months ago by lewisr

  • Milestone set to 1.4.1
  • Resolution set to fixed
  • Status changed from assigned to closed

I no longer see this with 1.4.1b1.

Test:

From C:\, I opened: C:\Programs\Lucide\Lucide.exe and opened a PDF. I browsed the PDF, closed it, then exited Lucide. There was no INI file in the root directory.

I repeated the above from a different drive/directory (D:\test). I started Lucide by typing the name of a PDF in the directory (4OS2 associates .PDF with Lucide). Lucide opened the document. I browsed, closed the document, then opened another from a different directory (same Lucide session). I then closed Lucide with that second document loaded. There was no INI in the original directory nor in the directory where the second PDF was located.

Note: See TracTickets for help on using tickets.