Hello XAF Team,
When using ConditionalAppearance to control visibility of tabs, the show/hide behavior is unstable. Sometimes it works, but sometimes it fails.
Please run the Web project of the attached VS2010 solution (v12.1.7). To learn how to re-produce this issue, please view the .mp4 video (attached in the first comment).
Regards,
James
To view the screen video, please see the attached ConditionalAppearanceTabs.mp4 file.
This appears to be a bug. Our developers will work on it.
Thanks Anatol for your confirmation.
~
This bug is a bit critical, because my business logic depends on the correct behavior, and now I got stuck.
Thank you for the information, James.
Hi James
We have analyzed this problem and found that it can be avoided by switching off WebApplication.DelayedViewItemsInitialization.
Alternatively, you can use simple groups in the layout instead of tabs. We will continue researching this problem and will return to you as soon as we have any results. Please bear with us.
Thanks Konstantin for your suggestions!
~
WebApplication.DelayedViewItemsInitialization is not a good idea, because that will significantly decrease the detail view loading performance (too long when entering the detail view).
~
If the nested list views are not organized via tabs, but are organized in simple groups, then there will be two layout issues in Web: (1) The UI style is not consistent (no Tab header), compared to other tabs-based nested list views; (2) The toolbar's width is larger than the nested list view (grid) itself.
~
So, it's better to resolve the described ConditionalAppearance compatibility issue with DelayedViewItemsInitialization (true) in Web UI.
Thank you for the feedback, James. We hope you continue discussing the suggested temporary solution in Control DelayedViewItemsInitialization in View Controllers. I am afraid we do not have other workarounds at the moment.
OK, thank you very much for your suggestions, Dennis. I'll try the workaround you provided in Q443212.