66e0650
Forego using dispatch_action for click handlers
Piotr Osiewicz
created
db39c3d
Fix porting mistake that caused clicking on the editor to misbehave (#3583)
Click to expand commit body
We used `width` instead of `height` in the "pixels-to-point" conversion
code, which would cause clicks to not work correctly when the width was
smaller than the `y` coordinate.
Release Notes:
- N/A
Antonio Scandurra
created
fdc0ef8
Maintain focus correctly when activating panes in zed2 (#3582)
Click to expand commit body
Previously, before emitting a `Focus` event from the pane inside of the
`focus_in` listener, we would erroneously check whether the pane's focus
handle was _not_ focused. However, by the time the pane was notified of
being "focused in", the focus handle would already be focused, which was
preventing the pane from ever emitting a `Focus` event. In turn, this
would cause the workspace to not maintain the active pane correctly.
This pull request maintains an explicit `was_focused` boolean as part of
the `Pane` state, which ensures we only emit the `Focus` event the first
time the pane receives focus.
As part of this, I also reworked how the outline view gets deployed to
allow clicking breadcrumbs even when the corresponding pane doesn't have
focus.
Release Notes:
- N/A
Antonio Scandurra
created
b4fc8ea
Fix porting mistake that caused clicking on the editor to misbehave
Click to expand commit body
We used `width` instead of `height` in the "pixels-to-point" conversion
code, which would cause clicks to not work correctly when the width was
smaller than the `y` coordinate.
fe315c6
Bind actions on the whole search bar, not just the query editor
Piotr Osiewicz
created
36d2ab4
Always open new project search view `workspace::NewSearch` action (#3581)
Kirill Bulatov
created
cdf7c10
Add an action to expand Rust macros with rust-analyzer (#3580)
Click to expand commit body
Deals with https://github.com/zed-industries/community/issues/1282
If rust-analyzer responds with non-empty message, opens a new singleton
multibuffer with the expansion result:

In gpui2, only editors with excerpts containing Rust languages get the
action, in gpui1 every editor (even the *.ts one) has this action
enabled but it does nothing.
Release Notes:
- Added an `editor::ExpandMacroRecursively` command to expand Rust
macros with rust-analyzer.
Kirill Bulatov
created
da44b51
Always open new project search view `workspace::NewSearch` action
- Restore impl_actions! and remove derive(Action)
Originally in gpui2 we inferred the action's namespace from the module
it was
defined in. This worked most of the time (ignoring the "remove_the_2"
hack),
but caused unintended (and mostly invisible) behavior in crates with
multiple
modules.
#3577 restored the namespace parameter to actions!, and this PR
reintroduces
`impl_actions!` to do the same for non-unit structs.
I considered trying to keep the struct-attribute API work, because it
does feel
more stylistically appropriate for rust, but two problems lead to it
feeling less good than `impl_actions!` in practice:
1. You have to repeat the namespace for each struct (and usually you're
defining them all in the same namespace)
2. You can't pass an argument to a derive macro inline, you need to use
an attribute instead.
Release Notes:
- N/A