We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Issue migrated from trac ticket # 3132
milestone: HeuristicLab 3.3.17 | component: Core | priority: medium
Views for items may be locked or set to readonly to prevent changes e.g. while an algorithm is running. HL allows multiple active views for the same item. This can lead to inconsistent lock states for views. For instance for the GA - TSP sample: Select BestKnownQuality parameter Start the algorithm --> the view for the parameter is locked Open another view for the BestKnownQuality parameter by double-clicking the ViewHost icon The value is locked in the new view (when the algorithm is still running) When the algorithm stops the view for BestKnownQuality is unlocked. However, the second view is still locked (expected: all views should be unlocked when the item is unlocked)
Views for items may be locked or set to readonly to prevent changes e.g. while an algorithm is running.
HL allows multiple active views for the same item. This can lead to inconsistent lock states for views.
For instance for the GA - TSP sample:
The text was updated successfully, but these errors were encountered:
s-wagner
No branches or pull requests
Issue migrated from trac ticket # 3132
milestone: HeuristicLab 3.3.17 | component: Core | priority: medium
2021-07-17 19:28:43: @gkronber created the issue
The text was updated successfully, but these errors were encountered: