View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003480JEDI VCL00 JVCL Componentspublic2006-01-30 18:002006-06-09 07:55
ReportertbolickAssigned Toobones 
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version3.00 
Target VersionFixed in Version3.30 
Summary0003480: jvAppIniFileStorage
DescriptionIf the Ini File cannot be written to on Flush, an exception is thrown. Since you cannot keep the Flush from happening automatically when the component is Destroyed, you always get an exception if the IniFile name points to an invalid drive. If, for example, you want to keep the Ini File on a USB or network drive which may become invalid before the program closes. Reads & Writes can be conditional (If FileExists), but the final Flush always happens.

Perhaps putting a try...except around the IniFile.UpdateFile would suffice.
TagsNo tags attached.

Activities

obones

2006-02-06 07:11

administrator   ~0008509

Interesting point, this needs to be discussed on the newsgroups here:

news://forums.talkto.net/jedi.vcl

obones

2006-06-09 07:55

administrator   ~0009554

An OnError handler has been added, called when Flush fails.

Issue History

Date Modified Username Field Change
2006-01-30 18:00 tbolick New Issue
2006-02-06 07:11 obones Note Added: 0008509
2006-02-06 07:11 obones Status new => acknowledged
2006-06-09 07:55 obones Status acknowledged => resolved
2006-06-09 07:55 obones Resolution open => fixed
2006-06-09 07:55 obones Assigned To => obones
2006-06-09 07:55 obones Note Added: 0009554