openframeworks / openframeworks/openFrameworks

Why don't ofCoreEvents forward a "source/sender" parameter?

Open
#5,642 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
10.4k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
9

Description

Our event system allows us to send the source as a const void* (a vestige of the Poco event system). I'm trying to identify what window certain events came from in a single app context and it seems like it would be easy pass on the source of a ofCoreEvent.notify call to the receiver.

Any reason why we aren't including source information @arturoc? I'm happy to add it, but want to make sure there wasn't an intentional reason you didn't do it previously.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the ofCoreEvents and ofCoreEvent.notify paths to understand how events reach receivers and where source information could be carried. Review existing event declarations and call sites before deciding the API behavior; done should mean receivers can identify the notifying source without breaking current event usage.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.