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
The update ontology table callback is called each time a character is typed in the textbox despite having the raise PreventUpdate statement early on. As the loading component is forced to run each time, it creates a delay/lag when you type alot of characters in quick succession. Very noticeable when testing locally on the Framework but less so on when deployed on GAE.
The text was updated successfully, but these errors were encountered:
One possible bandaid fix is to move the loading component over the search button instead of the table, so it would only show up when the user clicks search. However, not sure if it will still delay/lag as the update table callback is still called, but perhaps it's better visually
One possible bandaid fix is to move the loading component over the search button instead of the table, so it would only show up when the user clicks search. However, not sure if it will still delay/lag as the update table callback is still called, but perhaps it's better visually
Switched loading to button, don't think it helped much but it does look nicer
The update ontology table callback is called each time a character is typed in the textbox despite having the raise PreventUpdate statement early on. As the loading component is forced to run each time, it creates a delay/lag when you type alot of characters in quick succession. Very noticeable when testing locally on the Framework but less so on when deployed on GAE.
The text was updated successfully, but these errors were encountered: