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
I would have expected that the Find Patients UI should make it easy to switch to a different query. Currently, however, it involves moving the mouse to several, quite small targets:
As long as "Run Query" is only available on the "Find Patients" page, it makes sense to have query loading accessible only from this page too, and to make the UI more accessible. Alternatively, run and load query should be straight on the nav bar.
I'd also suggest that clicking anywhere on the saved query row should open it, rather than needing to click "Open".
Also, clicking "Open" for the query currently being edited results in a no-op with no UI feedback. Perhaps "Open" should be renamed to "Current" as a simple fix. (But when I look at the code I am not certain how to make the queries.current.id state available to the SavedQueriesTable component, so perhaps a simpler fix would just be adding dispatch(setNoClickModalState({ message: "Already Loaded", state: NotificationStates.Complete })); before returnhere.
PS @ndobb, please lmk if I'm spamming you excessively or if this is helpful!
The text was updated successfully, but these errors were encountered:
I would have expected that the Find Patients UI should make it easy to switch to a different query. Currently, however, it involves moving the mouse to several, quite small targets:
As long as "Run Query" is only available on the "Find Patients" page, it makes sense to have query loading accessible only from this page too, and to make the UI more accessible. Alternatively, run and load query should be straight on the nav bar.
I'd also suggest that clicking anywhere on the saved query row should open it, rather than needing to click "Open".
Also, clicking "Open" for the query currently being edited results in a no-op with no UI feedback. Perhaps "Open" should be renamed to "Current" as a simple fix. (But when I look at the code I am not certain how to make the
queries.current.id
state available to the SavedQueriesTable component, so perhaps a simpler fix would just be addingdispatch(setNoClickModalState({ message: "Already Loaded", state: NotificationStates.Complete }));
beforereturn
here.PS @ndobb, please lmk if I'm spamming you excessively or if this is helpful!
The text was updated successfully, but these errors were encountered: