Descriptive Problem Summary:
If you set the parent to none, it doesn't actually delete it.
Numbered Steps to Reproduce Problem:
1. Create a window with browse()
2. Delete it by winsetting its parent to none.
Expected Results:
It completely delete the window and clean up the browser context.
Actual Results:
It doesn't even hide the window.
Problem is consistent.
When does the problem NOT occur?
Never
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
It occurred in the past few BYOND versions if I remember correctly.
Workarounds:
You can only hide the window, not delete it.
ID:1995287
 Dec 8 2015, 8:10 pm
|
|||||||||||||
| |||||||||||||
|
Dec 8 2015, 8:20 pm
|
|
Rushnut
 |
This is true for input and alert too, however it can be accomplished by making a datum that calls browse and deleting the datum instead, it's not really a bug more just how windows are treated in DM.
|
Browse is a special cookie; you can access the browser element by suffixing ".browser" so its likely handled specially. I don't have time to verify if thats the case but I hope it is. Deleting the datum will not delete the windows that datum opened. (with browse, anyway)
| |
Setting the parent to null shouldn't work for a browser popup, because the new window doesn't have a parent. The browse() proc explains how to close the window.
| |
You can close it, but browse( null ) doesn't actually delete the browser, it just empties the content. They can stack up pretty quickly and gobble up memory if you use a lot of them.
| |