Replies: 5 comments
|
I think we'll have to think about how we can provide a global drag and drop callback that doesn't necessarily link to a control. FYI: here are some WIP improvements to DND: #1123 |
|
I see, so as is right now, it's impossible to do that right? And if I understand correct, #1064 should provide that functionality. |
|
I’m not sure it’s impossible right now and currently that pr doesn’t
address it. It might give you some ideas though how you can hack it for
your purposes. If you think what you do is good enough feel free to make a
PR
…On Wed, 7 Aug 2024 at 20:55, Achilleas Villiotis ***@***.***> wrote:
I see, so as is right now, it's impossible to do that right? And if I
understand correct, #1064 <#1064>
should provide that functionality.
—
Reply to this email directly, view it on GitHub
<#1122 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFACLVUYMKGPWVCKV76PILZQJURJAVCNFSM6AAAAABMEYFRKSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMRWG44DGNA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
I would be interested in giving it a try, however I only just started using the framework? Is there anywhere I could start trying to figure this out? Perhaps a new IControl subclass with mouse event passthrough or something like that? I'd love to try! |
|
I made an issue: #1126 I would probably take the approach that is used with the "key handler func" for receiving global key presses https://github.com/search?q=repo%3AiPlug2%2FiPlug2%20keyHandlerFunc&type=code |
Uh oh!
There was an error while loading. Please reload this page.
As the title suggests, I tried creating an IControl inherited class, that would handle onDrop. However, it blocks everything else for the controls below. In the same spirit, placing it at the bottom layer, it isn't accessible.
Is there a way to allow mouse event "passthroughs" or something similar? How would you go about adding onDrop capabilities to the whole plugin window?
Thanks!
All reactions