IzPack

Lost input data when navigating forward/backward in installer

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 4.0.1
  • Fix Version/s: 4.1.0
  • Component/s: Installer
  • Labels:
    None
  • Environment:
    windows
  • Number of attachments :
    0

Description

When entering data in input fields of the GUI-driven installer this data is lost after going "next" and "back".

The field is defined as a RuleInputField
<field type="rule"> ...

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dennis Reil added a comment -

This can be solved by using condition's on fields and use the input from the associated variables.

Show
Dennis Reil added a comment - This can be solved by using condition's on fields and use the input from the associated variables.
Hide
Permalink
Julien Ponge added a comment -

Closed following Dennis's comment.

Show
Julien Ponge added a comment - Closed following Dennis's comment.
Hide
Permalink
Thomas Bopp added a comment -

also I am expecting this as default behaviour I am currently not able to find out how this is really done.
Could you provide some example, please?

What about this:
<field type="rule" variable="WEB_SERVICE_PORT">
<spec txt="WebService Port" layout="N:4:5" set="0:8083" id="web.service.label" />
</field>

is there any documentation on conditions?

Show
Thomas Bopp added a comment - also I am expecting this as default behaviour I am currently not able to find out how this is really done. Could you provide some example, please? What about this: <field type="rule" variable="WEB_SERVICE_PORT"> <spec txt="WebService Port" layout="N:4:5" set="0:8083" id="web.service.label" /> </field> is there any documentation on conditions?
Hide
Permalink
Jochen Hinrichsen added a comment -

Dennis, Julien,

i'm not sure if setting this ticket to 'Resolved' 'Closed' is a good choice. IMHO the default behaviour of an application is to treat user input as first class data, overruling any default values used in 'set' attributes. User Input should be stored and restored accordingly when navigating through panels, users tend to get frustrated when entering the same values again and again just because they hit 'back'. Displaying what the user has entered is the principle of least astonishment.

Although i do not like the idea of adding a condition to my three dozen of variables, but i'd be more than happy if we had this documented somewhere.

Just my $.02

Jochen

Show
Jochen Hinrichsen added a comment - Dennis, Julien, i'm not sure if setting this ticket to 'Resolved' 'Closed' is a good choice. IMHO the default behaviour of an application is to treat user input as first class data, overruling any default values used in 'set' attributes. User Input should be stored and restored accordingly when navigating through panels, users tend to get frustrated when entering the same values again and again just because they hit 'back'. Displaying what the user has entered is the principle of least astonishment. Although i do not like the idea of adding a condition to my three dozen of variables, but i'd be more than happy if we had this documented somewhere. Just my $.02 Jochen

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.