Bug in TextBoxCommandInput and StringValueInput inside a table hosted by a group
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Usign TextBoxCommandInput and StringValueInput inside a TableCommandInput which is a child of a GroupCommandInput produces some unexpected behaviours.
For StringValueInput:
Setting isReadOnly to true for StringValueInput will not work if the StreingValueInput is inside a table which is a child of a group.
The following picture shows the problem in a modified version of CustomGraphicsSample add-in (left) versus the original version of the sample add-in (right). The difference is that the modified version uses a group to host the table.
For TextBoxCommandInput:
Using TextBoxCommandInput inside a TableCommandInput which is a child of a GroupCommandInput produces some problems when the number of rows is greater than TableCommandInput.maximumVisibleRows. It actually creates empty a textbox with a small vertical scrollbar for the rows > maximumVisibleRows.
The following picture shows the problem in a modified version of CustomGraphicsSample add-in (left) versus the original version of the sample add-in (right)
Website: https://perceptino.com