Please take look at my screenshots for a better context:
I have a Query widget and Table widget. However, whenever I get the result from Query, it will not automatically switch to the corresponding table tab, (the 3rd screenshot). I must do it manually.
From a user's standpoint, it may be confusing if they are using it for the first time. They might not notice Query will not do the job automatically for them, and they then instead wondering why there is no result displayed.
This is a good point. But why not use the query output view as the default table view to save the hassle of seeing the data without changing the sheets in the table?
Also in your case, the query result is generated at run time, so I would prefer to use View in table or Add to table data actions to view the result in the table. Like the other preset table sheets, the query output view is used for display data so I think it should not be connected to the query widget unless there are some message actions between them (actually there's no such action available).
Apologize in advance for necro-replying to a topic but I'm currently dealing with this. You asked why not use the query output view and here's why I don't like/want to do this:
I have the query widget hitting a feature class with 2 related tables. I have to keep drilling down by tapping the 4 dots to access the options pane and then select related records. This is a far more confusing UI than if the query widget would filter the table widget after selecting records. If it did that, in my example each table is its own tab which the user can quickly cycle through and then export the records via the 4 dot pane located on each tab. *That's* what I want to do but it does not do.
You can select View in Table of Add to Table but the user has to select that option. IMO, the action should AUTOMATICALLY do this, if specified.