-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add BreakBeforePoint + Break on component lifecycle #206
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Nyan11 I think we need to clarify two cases:
- Object Centric Breakpoint
- No-Object Centric Breackpoint (classic)
This can be done by explicit labels (not sur to know if this OCB or not).
Other remark:
- A component can be re-activated after passivation, not only when a new component is create. This is why I'm asking on top. Example: Can I add a breakpoint on passivate for "this" component (#default) of for all components with this "component type"?
I agree, i think there should be 2 type of logos:
This change should be done also in the PharoDebugger project.
In the inspector of deployed components:
In the browser:
|
Currenlty there is a bug on object centric breakpoint (see: pharo-project/pharo#17808), that does not allow to open the Debug Point Browser if you use the object-centric debug point. You need to clear them all using the "Remove All Debug Points" in the same menu. Also there are problem with object-centric breakpoint in GPS example with the fork. If you try to put it in the Events of MolGNSGPS it will not trigger. It should trigger inside the Pictures |
No description provided.