If you create it in the following form and change the is_open_window value, isn't this what you want?

            let mut is_open_window: bool = true;

            egui::Window::new("test")
            .open(&mut is_open_window)
            .show(ui.ctx(), |ui| {
                ui.label("test test test");
            });

Of course, this is an example, and is_open_window must maintain its value in an external variable or struct.

If you create it in the following form and change the is_open_window value, isn't this what you want?

            let mut is_open_window: bool = true;

            egui::Window::new("test")
            .open(&mut is_open_window)
            .show(ui.ctx(), |ui| {
                ui.label("test test test");
            });

Of course, this is an example, and is_open_window must maintain its value in an external variable or struct.

.open(&mut is_open_window) will show an extra close button in the window title bar, in my case I don't want the window to be able to be closed manually by the user.

.open(&mut is_open_window) will show an extra close button in the window title bar, in my case I don't want the window to be able to be closed manually by the user.

If .open() is not set, the close button will not be created. Is this what you want?

             egui::Window::new("test")
             .show(ui.ctx(), |ui| {
                 ui.label("test test test");
             });

If .open() is not set, the close button will not be created. Is this what you want?

             egui::Window::new("test")
             .show(ui.ctx(), |ui| {
                 ui.label("test test test");
             });

Often we can just use the following code, as examples/confirm_exit does:

let mut is_open_window: bool = true;

if is_open_window {
    egui::Window::new("test")
    .show(ui.ctx(), |ui| {
        ui.label("test test test");
    });
}

But the above code will not show the window closing animation when the window is closed. So I would like to have a .open that doesn't create a close button in the window title bar.

But the above code will not show the window closing animation when the window is closed. So I would like to have a .open that doesn't create a close button in the window title bar.

I'm not sure what the difference is in closing animation.
However, I think it would be better to have a separate function to select close button.

Please apply #4334, and let us know the results.
I don't know if PR #4334 will be approved.

• close button on/off in egui::Window #4334

I'm not sure what the difference is in closing animation. However, I think it would be better to have a separate function to select close button.

Please apply #4334, and let us know the results. I don't know if PR #4334 will be approved.

• close button on/off in egui::Window #4334

Thanks for the PR, but I have one too, though it seems our PRs don't conflict.
I don't think the user should be allowed to control whether or not the close button is displayed, as it would conflict with .open.

Thanks for the PR, but I have one too, though it seems our PRs don't conflict. I don't think the user should be allowed to control whether or not the close button is displayed, as it would conflict with .open.

Because of 'clippy' and 'rust fmt', it is now complete.

This is can only turn on/off the close button,
It does not conflict with open() .

Because of 'clippy' and 'rust fmt', it is now complete.

This is can only turn on/off the close button, It does not conflict with open() .

Because open() requires a mut reference of type bool, and the close button is the only place where this mut reference is needed, if the user will not need the
close button, then the mut reference should not be passed into open(), but rather a value or immutable reference.

#4334 turns on/off only the close button.
#4334 is does not conflict with open() .
The variables used in open() can be used the same as before.

#4334 turns on/off only the close button. #4334 is does not conflict with open() . The variables used in open() can be used the same as before.

Yes, but .open requires a mut reference to the variable, and the user will think that the variable might be changed by the window, but if the close button is turned off, the variable will never actually change, and you might want to note this in the closebutton documentation.