[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haiku-bugs
Subject:    [haiku-bugs] Re: [Haiku] #18251: Add mechanism to BDeskbar to locate replicant views
From:       "Haiku" <trac () haiku-os ! org>
Date:       2023-02-24 19:29:16
Message-ID: 063.7ff1e2a36964eabe482bc23a38d49b15 () haiku-os ! org
[Download RAW message or body]

--===============1507181529168358542==
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

#18251: Add mechanism to BDeskbar to locate replicant views
---------------------------------+-------------------------
  Reporter:  waddlesplash        |      Owner:  nobody
      Type:  enhancement         |     Status:  new
  Priority:  normal              |  Milestone:  Unscheduled
 Component:  Kits/Interface Kit  |    Version:  R1/beta4
Resolution:                      |   Keywords:
Blocked By:  18206               |   Blocking:
  Platform:  All                 |
---------------------------------+-------------------------
Comment (by pulkomandy):

 The code in BWindow actually does a lot of efforts to keep them in sync.
 Setting the window title will rename the thread, rename the BHandler, etc.

 But I think we can fix this without having to change the name at all.

 The replicant itself should be able to get it simply by calling Looper()
 from its AttahcedToWindow() method.

 If the app that adds the replicant needs a handle to the window to
 communicate with it, it should be able to get it from the reply to the
 kMsgAddAddOn or kMsgAddView message used to add something to Deskbar.
 Seems like a reasonably simple change to BDeskBar::AddItem: we already get
 the reply message there, we just need to find the looper which sent it,
 and allow the caller app to get a BMessenger to it in return.
-- =

Ticket URL: <https://dev.haiku-os.org/ticket/18251#comment:10>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
--===============1507181529168358542==--

[prev in list] [next in list] [prev in thread] [next in thread]