Jason Lee
1887a6db53
Release Notes: - N/A ---- Continue #14044 for Windows ## The problem The `cx.open_window` method has provided us a `window_kind` option to allows creating a Popup kind. This behavior can work on macOS, the popup kind window have no-border, no-shadow, no-resize, and followed the `is_movable` if present true it can't move. This PR to fix those supports on Windows. The border and shadow still exist, I have tried to use WS_POPUP window_style, but it will crash: > This is looks like complex, it is out of my known. ``` Blocking waiting for file lock on build directory Compiling gpui v0.1.0 (F:\work\zed\crates\gpui) Finished `dev` profile [unoptimized + debuginfo] target(s) in 13.96s Running `target\debug\examples\window_positioning.exe` thread 'main' panicked at F:\Users\jason\.cargo\git\checkouts\blade-b2bcd1de1cf7ab6a\21a56f7\blade-graphics\src\vulkan\init.rs:864:18: called `Result::unwrap()` on an `Err` value: ERROR_OUT_OF_DEVICE_MEMORY note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace error: process didn't exit successfully: `target\debug\examples\window_positioning.exe` (exit code: 0xc0000409, STATUS_STACK_BUFFER_OVERRUN) ``` So I just make a simple change, to use `WS_EX_TOOLWINDOW` this can disable resize, and connect `is_movable` to `handle_hit_test_msg` to disable move, and also no Status Bar icon. ## Before https://github.com/zed-industries/zed/assets/5518/76740a71-e0ba-401f-958d-f4afdeb417c6 ## After https://github.com/zed-industries/zed/assets/5518/dca49f13-914c-425a-b8b6-b9fc15f8d208
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.