#16284: Scripting messages sent to window that not started message loop cause
freeze or timeout
---------------------------------+----------------------------
Reporter: X512 | Owner: nobody
Type: bug | Status: new
Priority: normal | Milestone: Unscheduled
Component: Kits/Interface Kit | Version: R1/Development
Resolution: | Keywords: scripting
Blocked By: | Blocking:
Platform: All |
---------------------------------+----------------------------
Comment (by ttcoder):
I do this in some apps:
{{{
BWindow win = new ......
win->Hide();
win->Show();
}}}
That gets the message loop going, _without_ showing the window on screen
(since the call to Show() gets the show count from -1 to 0, instead of
from 0 to 1).
Doing that solves a bunch of different issues, only one of which overlaps
with this ticket (scripting). So I guess my point is, you've touched a
somewhat sticky point of the BeOS/Haiku API here : scripting is only one
of the things that is impacted by the BWindow API semantics. Going into
R2, it might be worth including this discussion in the overall API
overhaul discussions. So what to do... Pulkomandy could just use the above
trick on the Web+ Console window and close this ticket, or we could do the
scripting-specific work-arounds suggested above (in fact they seem to make
sense regardless of what is done with the rest of the API), or we postpone
this to R2 if not happy with work-arounds and in a quest to the ultimate
fix 8-)
--
Ticket URL: <https://dev.haiku-os.org/ticket/16284#comment:2>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
