2022-01-30, 02:29
@amasephy
Your observations give me a hard time.
The index behaves really weird when the view is set to "automatic content insets". The misbehavior / vertical offset depends on the text which is used for the index. I am at the end of my possibilities and will stop researching this.
The use case with Global Search and the default pane is also just about marking the wrong menu, right? What should be possible without too much hassle is to unmark/deselect the current menu. But marking the menu entry for the default pane seems to require more coding than I feel appropriate. I will look at this tomorrow, but am not sure I will find an elegant solution ...
The issue in the video I will look at. Should not be too much of an issue.
The search box width is reduced by iOS when the table view's index is shown. I am not sure how to avoid this. In the grid view this does not happen as another index implementation is used.
Your observations give me a hard time.
The index behaves really weird when the view is set to "automatic content insets". The misbehavior / vertical offset depends on the text which is used for the index. I am at the end of my possibilities and will stop researching this.
The use case with Global Search and the default pane is also just about marking the wrong menu, right? What should be possible without too much hassle is to unmark/deselect the current menu. But marking the menu entry for the default pane seems to require more coding than I feel appropriate. I will look at this tomorrow, but am not sure I will find an elegant solution ...
The issue in the video I will look at. Should not be too much of an issue.
The search box width is reduced by iOS when the table view's index is shown. I am not sure how to avoid this. In the grid view this does not happen as another index implementation is used.
