Can't delete an adjacent window when window is maximized

[ronburk]

In emacs, Ctrl-X 0 just deletes the current window. This works fine in
SlickEdit for individual MDI windows. However, when my MDI window
is maximized and I type Ctrl-X 0, I get the

 "Can't delete an adjacent window when window is maximized"

However, I can still just click on the MDI close button (the little 'X'
below the big 'X' of the main window close button). Is there any way
to make Ctrl-X 0 just mean "do the same thing as clicking on the
MDI close button, whether the MDI child window is maximized or not"?

I just want the darn window to close! :-).

[Clark]

There are ambiguities here.  Closing a window does not close any buffers.  If the maximized window is closed, there will be buffers remaining but no window to view them in.  Do you want all buffers closed? Do you just want the current buffer closed?  Or do you want to close the window and you don't care if you can't view your buffers?

[ronburk]

I want Ctrl-X 0 to do exactly the same thing as reaching up
with the mouse and clicking on the 'X' (close window) button
of the current MDI window/pane. Despite the astounding array
of potential ambiguities, that button seems to have a very
clear meaning (and result) -- I just want a keystroke that
does that (and that happens to be pretty much exactly what
Ctrl-X 0 does in emacs, in my limited experience).

In fact, I'm pretty sure Ctrl-X 0 just "did the right thing" in
older versions of VS, and just got broke somewhere along
the way (maybe with the introduction of the tabbed version
of child MDI windows), but I could be mistaken.

[Clark]

Looks like this makes sense since the change that Dennis made to close_window. In 11.02, SlickEdit does not close the window until the last buffer is closed.  This makes close_window identical to close_buffer.  So let me make sure I understand what you want.  If you have one maximized window and 4 buffers open, you want to Ctrl-X '0' to close the current buffer right?