I think the getEventUserData isn't properly implemented. If I understand it correctly, it should return a separate object for each widget

Yea that's what getEventUserData should do.

I think Capy uses native apis in both gtk and win32 apis for attaching custom data to widgets, but I'm not aware of something similar in macos. Perhaps we could just have a global hashmap, with the peer as key? Or would that leak?

You can absolutely use a global hashmap for this usecase. Although, for the WebAssembly backend, when I faced the same problem, I ended up replacing the peer object by a manually allocated GuiWidget, which basically contains EventUserData's fields, alongside the actual peer object (which would be objc.Object).

So for the macOS backend, this would be equivalent to replacing, in Label and in Container, the field peer: objc.Object by peer: GuiWidget.
And creating the struct:

const GuiWidget = struct {
  object: objc.Object,
  // Either include EventUserData or just copy its fields. Although including
  // it might be better.
  data: EventUserData,
};

Then in Label.init and Container.init, you allocate an instance of GuiWidget and fill in the data.

Macos backend needs a window delegate to capture events. #100

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions