Opened 14 years ago

Closed 13 years ago

#259 closed defect (fixed)

GLI client (and standalone??) saving config file

Reported by: kjdon Owned by: ak19
Priority: moderate Milestone: Release 2.82
Component: GLI Severity: blocker
Keywords: Cc:

Description

When starting up the GLI client, you are asked for library and gliserver.pl address. You enter these and the GLI opens up. It should save the file at this point. I am testing the problem of collections not opening on John Rose's computer, and when I try to open a collection, sometimes it hangs. I Ctrl-C to kill it, and the config file is not saved so I need to enter the library address again next time. Better that it had saved it already.

Change History (4)

comment:1 by kjdon, 14 years ago

Milestone: Next Release (2 or 3)

comment:2 by davidb, 13 years ago

Milestone: Next Release (2 or 3)Release 2.82
Severity: blocker

comment:3 by davidb, 13 years ago

Owner: changed from nobody to ak19

comment:4 by ak19, 13 years ago

Resolution: fixed
Status: newclosed

Fixed and checked.

This was already fixed as a side-effect of my tinkering with Remote Greenstone server stuff. The URLField.java's store() method is called by WarningDialog.java which instantiates the input URL field into which the user enters the gliserver.pl URL. When the user clicks OK in the input dialog presented by WarningDialog, the URLField.store() is called to save the changes to the Configuration to the config file.

The saving was done for the DropDown control into which the user could enter the gliserver.pl URL or from which they could choose one they typed in earlier. Now the Configuration is also set to save upon calling URLField.store() in case anyone uses the URLField.Text textfield control for any similar purpose.

Note: See TracTickets for help on using tickets.