Skip to content

Add "dirty checking" to expression builder #70

Open
@GoogleCodeExporter

Description

@GoogleCodeExporter
The expression builder should know when an expression has/hasn't changed so we 
can do the following:

1) Provide visual indication to the user that the expression is in an unsaved 
state
2) Reduce the number of confirmation dialogs.  If an expression hasn't changed, 
then loading a new one shouldn't cause an "Are you sure?" dialog.  It's 
currently pretty annoying to always have to go through the confirmation dialog 
when all you want to do is double-click on several expressions just to test 
them and see how they work on the robot.

Original issue reported on code.google.com by garthabr...@gmail.com on 24 Oct 2011 at 3:20

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions