You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I click on another project, the visual selection stays at the top project, even though the other panes of the browser are updated. However, I cannot select the top project anymore because, visually, it still is selected, in contrast to the state of the model. Moving the selection with the up and down keys also does not work.
The list uses index-based access via the variable projectIndex in SquitBrowser.
@marceltaeumel Can you please have a look or delegate to the colleagues who were involved in the latest list morph changes? If I used the API wrong, please suggest a fix.
The text was updated successfully, but these errors were encountered:
Yes, due to a different caching strategy in pluggable lists, faulty (or lazy) models might reveal such effects now.
PluggableListMorph >> #verifyContents does not work because your model (i.e., SquitBrowser) is no CodeHolder, which implements #stepIn: etc. for the "smart updating" preference.
The model SquitBrowser fails to tell the views about the new selection in #refresh.
When I click on another project, the visual selection stays at the top project, even though the other panes of the browser are updated. However, I cannot select the top project anymore because, visually, it still is selected, in contrast to the state of the model. Moving the selection with the up and down keys also does not work.
The list uses index-based access via the variable projectIndex in SquitBrowser.
@marceltaeumel Can you please have a look or delegate to the colleagues who were involved in the latest list morph changes? If I used the API wrong, please suggest a fix.
The text was updated successfully, but these errors were encountered: