1. The recently introduced PropertySheet control is very useful, but supports only a limited number of exposed methods, e.g. .ModeSwitcherVisible = True/False. So is there a way (likely using a native Java method call) to set a property sheet to display either in list or accordion mode? {Currently, it always defaults to the list mode (even when multiple categories have been defined via its meta map).}
2. Can additional field types be added (e.g. sliders, dropdown combobox, etc.)? Or will that possibly be coming in future B4J releases?
3. I see no way to set focus to a specific, or get focus of the current/active, property sheet field. Possible?
4. Since there are no exposed events, how can it be determined when a field value has changed in order to conditionally act on (e.g. save property selections and/or entries to a file, or update something else in UI as a direct result)? I've seen where someone used a timer to simply capture all field values every few seconds, but that seems quite inefficient when dealing with large and/or multiple property sheets.
*And, I've at least encountered a UI problem (bug?) when a property sheet has [meta map] .SetChoices fields -- as their dropdown listbox background color displays as transparent, albeit *only if/when* the property sheet is added to the app's main form (problem does not happen when it's added to a popup/secondary form). I can provide an example re: this if it's not been encountered/reported before.
2. Can additional field types be added (e.g. sliders, dropdown combobox, etc.)? Or will that possibly be coming in future B4J releases?
3. I see no way to set focus to a specific, or get focus of the current/active, property sheet field. Possible?
4. Since there are no exposed events, how can it be determined when a field value has changed in order to conditionally act on (e.g. save property selections and/or entries to a file, or update something else in UI as a direct result)? I've seen where someone used a timer to simply capture all field values every few seconds, but that seems quite inefficient when dealing with large and/or multiple property sheets.
*And, I've at least encountered a UI problem (bug?) when a property sheet has [meta map] .SetChoices fields -- as their dropdown listbox background color displays as transparent, albeit *only if/when* the property sheet is added to the app's main form (problem does not happen when it's added to a popup/secondary form). I can provide an example re: this if it's not been encountered/reported before.