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
Conversation
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().
IzPack project » izpack #679 SUCCESS |
Unfortunately this breaks the latest implementation of blocking variables reserved by panels. |
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.
IzPack project » izpack #680 SUCCESS |
The last update does resolve a loop for a variable with several conditions. |
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. |
Izpack 1182: Evaluation of dynamic variables, which depends on other ones
It works so far, well-done. |
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.