Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Izpack 1182: Evaluation of dynamic variables, which depends on other ones #306

Merged
merged 8 commits into from Jan 30, 2015

Conversation

Helpstone
Copy link
Collaborator

With this fix the dynamic variables, which depend on other ones, are computated correct on the first refresh() already. The Issue is olved with this pull request.

state is reached. This is important for dynamic variables, which depend
on other dynamic variables.
state is reached. This is important for dynamic variables, which depend
on other dynamic variables.
A dynamic variable with checkonce="true" can be updated several times
during ONE SINGLE call of DefaultVariables.refresh() and should be fixed
("checked") at the end of this refresh(), not during the refresh().
@buildhive
Copy link

IzPack project » izpack #679 SUCCESS
This pull request looks good
(what's this?)

@rkrell
Copy link
Member

rkrell commented Jan 28, 2015

Unfortunately this breaks the latest implementation of blocking variables reserved by panels.
I will check this, soon.

http://docs.codehaus.org/display/IZPACK/Lifecycle+of+dynamic+variables

<dynamicvariables>
  <variable name="thechoice" value="fallback value" />
  <variable name="thechoice" value="choice1" condition="cond1" />
  <variable name="thechoice" value="choice2" condition="cond2" />
</dynamicvariables>
<conditions>
  <condition type="variable" id="cond1">
    <name>condvar1</name> <value>1</value>
  </condition>
  <condition type="variable" id="cond2">
    <name>condvar1</name> <value>1</value>
  </condition>
</conditions>
(will become better readable after the next change)
different condition the check for "changed" must be done after all
dynamicvariables have been computated.
@buildhive
Copy link

IzPack project » izpack #680 SUCCESS
This pull request looks good
(what's this?)

@Helpstone
Copy link
Collaborator Author

The last update does resolve a loop for a variable with several conditions.
Does this also resolve your problem wirh blocking variables (which probably also have several conditions)?
I'll do some more testing and probably implement a check for loops

@rkrell
Copy link
Member

rkrell commented Jan 29, 2015

I'll check this soon, but it should not break older environments, relying on the order of definition of the dynamic variables. Thanks for your action.

rkrell added a commit that referenced this pull request Jan 30, 2015
Izpack 1182: Evaluation of dynamic variables, which depends on other ones
@rkrell rkrell merged commit 62ac85c into izpack:master Jan 30, 2015
@rkrell
Copy link
Member

rkrell commented Jan 30, 2015

It works so far, well-done.
Thank you.

@rkrell rkrell added the bug label Jan 30, 2015
@rkrell rkrell added this to the 5.0 RC5 milestone Jan 30, 2015
@rkrell rkrell self-assigned this Jan 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
3 participants