Skip to content
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

Adding breakpoint (in margin) saves a dirty editor without asking, and doesn't show the breakpoint. #2793

Open
fuhrmanator opened this Issue Mar 11, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@fuhrmanator
Copy link

fuhrmanator commented Mar 11, 2019

I'm using Pharo 7.0.2 on Windows with a 32-bit image from Moose CI.

If I'm editing a method and I click the margin to insert a breakpoint, it seems the editor is saved, and I also don't see the breakpoint.

Steps to reproduce:

  1. Edit a method (making it dirty in the editor). Confirm the upper right corner of the editor is orange.
  2. Insert a break point by clicking the left margin next to an instruction.
    1. Confirm that no breakpoint is visible in the margin (even though I think it was actually added and saved).
    2. Confirm that the editor complains it has been saved elsewhere; its upper right corner is red.
  3. If you try to save, you get a (scary) warning that your editor "may have been changed elsewhere."
  4. If you cancel (Ctrl-L) you see the breakpoint is in the margin.

Suggested solution: I would be happy as a developer if the system would not allow me to insert breakpoints in unsaved (dirty) methods (e.g., I would see a warning dialog saying I must save my method first).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.