Opened 19 years ago
Last modified 17 years ago
#505 closed bug
First click on BMenuBar will show empty MenuWindow — at Version 8
Reported by: | diver | Owned by: | axeld |
---|---|---|---|
Priority: | low | Milestone: | R1 |
Component: | - General | Version: | |
Keywords: | Cc: | kaoutsis@… | |
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
First click on BMenuBar will show empty BPopUpMenu list, half second later menu items will appear.
Change History (8)
comment:1 by , 19 years ago
comment:3 by , 19 years ago
Summary: | First click on BMenuBar will show empty BPopUpMenu list → First click on BMenuBar will show empty MenuWindow |
---|
comment:4 by , 19 years ago
So we have to find out why it's taking so much time to create the menu window.
comment:5 by , 19 years ago
I might have found out what's happening: BMenu::AttachedToWindow() calls get_key_map(). get_key_map() calls control_input_server(). If it's the first time that application calls that method, a BMessenger is created using this constructor: BMessenger(const char *signature) (it's cached later), and that might be the reason for the slow start (and not the window creation as I said before, as the window is obviously shown on screen immediately).
comment:7 by , 19 years ago
Owner: | changed from | to
---|
comment:8 by , 18 years ago
Description: | modified (diff) |
---|---|
Owner: | changed from | to
Platform: | → All |
Reassign to Axel, because the culprit seems to be windows creation + first show. Feel free to reassign it to me if you find out it's not the case.
First click on any menubar causes a new BWindow to be created, maybe that's what is taking so much time ? By the way, On real hardware or emulated ? I definitely can see this on vmware.