LeoMobileDeveloper / LeoMobileDeveloper/Blogs
UIResponder+QTEventBus
Open
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 1.6k
- Forks
- 295
- PR merge metrics
- No merged PRs in 30d
Description
- (QTEventBus *)eventDispatcher{
UIResponder * resp = self;
do {
if ([resp isDispatcherProvider]) {
return resp.qt_privateBus;
}
resp = resp.nextResponder;
} while (resp != nil);
return nil;
}
这样实现，如果VC view的子view也设置为dispatcherProvider VC中的事件就不能回调了
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the UIResponder+QTEventBus entry point shown in the issue and trace the responder chain when both a view controller view and one of its subviews are dispatcher providers. Reproduce the nested-provider case and verify that events intended for the view controller still reach it; done means the reported callback failure no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, objective-c
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100