Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#52 closed defect (invalid)

Creep points can't be deactivated or removed

Reported by: ke Owned by: jd
Priority: minor Milestone:
Component: core Version:
Keywords: Cc:


Doing so in the creeppoint editor and clicking "Apply and quit" has no effect. Test case: deactivate or remove the default creep and skip points for grammar compilation – the behavior doesn't change, compilation isn't shown.

Are other point editors, adding points etc. also affected?

Change History (6)

comment:1 Changed 8 years ago by jd

Hmmm. Since the skip point is applied right away (before you have a chance to deactivate it), this is not exactly surprising behavior. Or do you mean if you compile the grammar a second time? The behavior in that case is still somewhat inconsistent anyway, at least when I am calling dcompile_gram a second time from console (the Parse menu items are still greyed out in my version).

comment:2 Changed 8 years ago by ke

  • Resolution set to invalid
  • Status changed from new to closed

Sorry, my bad. It is possible to bring up the Kahina GUI by using the new dgo/0 predicate and thus to manipulate breakpoints before any steps arrive from the debugger. However, starting a compilation or parsing process also always starts a new Kahina session with the same GUI, but with a new tree behavior. And since default breakpoints are currently created with the tree behavior, any changes the user made to breakpoints are lost, so this is indeed expected behavior.

That at the moment every session starts with the default sets of breakpoints is not so desirable, of course, but issue #51 addresses this anyway.

comment:3 Changed 8 years ago by TarasBulba

  • Cc Queens added
  • Summary changed from Creep points can't be deactivated or removed to Edgewall880 Software857

comment:4 Changed 8 years ago by ke

  • Summary changed from Edgewall880 Software857 to Creep points can't be deactivated or removed

comment:5 Changed 8 years ago by ke

  • Cc Queens removed
Note: See TracTickets for help on using tickets.