Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1
Issue: Table and inner widget interactivity
Seems
egui
PR emilk/egui#2244 blocks interaction of underlying table column widgets when table interaction is enabled. To address this issue, currently separated window is created upon table area to activate 'editor view', which is not desirable.This seems comes from(not bug)
egui_extras::Layout::add
method that is invoked byTableRow::col
._::Layout::add
callsself.cell(.., add_cell_contents)
before calling intoself.ui.allocate_rect
for retrieving cell interaction, which simply covers interaction area of user-requested ui fromadd_cell_contents
.Prior to egui 0.20(from mentioned PR), it was just okay since there were no input priority between widgets within same area. However, afther the PR, it seems widget interaction now have kinda 'latest first' priority, which prevents passing-through user interactions.
However, I don't know why the egui web demo page works with this well; perhaps its version is less than 0.20? Otherwise, it'll be my setup issue? Should be tested with wasm32 build either...