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.

Sign up for GitHub

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

Updated docu for VM controls in Flex #55

Merged
merged 3 commits into from
Apr 27, 2023
Merged

Updated docu for VM controls in Flex #55

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2bdfb09
Updated docu for VM controls
dstork Apr 26, 2023
51109f2
Update docs/05_Developing_Apps/enabling-ui-adaptation-other-things-to…
dstork Apr 27, 2023
5fa9785
Update docs/05_Developing_Apps/enabling-ui-adaptation-other-things-to…
dstork Apr 27, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/05_Developing_Apps/enabling-ui-adaptation-other-things-to-consider-de9fd55.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,9 @@ If users should be able to save their UI changes as different views \(control va

All you have to do is add this control to an appropriate location in your app, and assign the desired UI container as a target in a `for` association.

Please note that it is not supported to retroactively introduce a variant management control after a key user has already created adaptations for your application. This would lead to adaptations being applied in a non-defined order, making the state of the UI unpredictable.

If you retroactively remove a variant management control for which key user adaptations or end user personalization already exist, these adaptations will be lost.

<a name="loiode9fd55c69af4b46863f5d26b5d796c4__section_rvb_cpn_2jb"/>

Expand Down