Clicking the X on a DockableContent doesn't appear to actually close anything, it just hides it.
I need the window to actually close and release its resources and data.
It appears that I might be able to track the items I add to the DockablePane and remove them from the Items collection at a later time, but there doesn't appear to be any way for me to detect that the X has been pressed or the window closed, at least not
without writing some really ugly code that it makes no sense I should have to write.
Sadly, this is kind of a deal breaker for me so it's not clear I can actually use this otherwise pretty nice package. If not, it's obviously irrelevant *why* this design choice was made but I still have a slight intellectual curiosity as to the rationale
behind such a decision. I can't think of any reasonable scenario where a user would expect clicking on an X is not clearly a closing gesture, as opposed to simply a hiding gesture.
Even in Visual Studio, which I presume to be the design motivation for this package, as a user, I assume that clicking the X on a docked window closes that window and releases the resources that window consumes.
Anyway, it's obviously of minor importance. I was just wondering if there was an explanation...some consideration I overlooked in how a dockable window package would have to be designed.