Opened 12 years ago

Closed 12 years ago

Last modified 10 years ago

#138 closed Feature request (fixed)

Automatic plugin validation leads to unexpected behaviour

Reported by: Matthäus Wander Owned by: Thomas Schmid
Priority: Important Milestone:
Component: AnotherEditor Keywords:


Developers of complex plugins get confused about the automatic plugin validation, that takes places by the editor when a plugin is pulled into the workspace. For long running plugins it's not useful, as it may block the GUI (or lead to CPU-intensive calculations in background thread). From inside the plugin you can't decide whether the validation is running or the plugin is executed normally, therefore you can't prevent unncessary longer runs.

I propose to use unit tests or some external (half-)automatic testing method instead of the current validation feature.

Change History (3)

comment:1 Changed 12 years ago by Matthäus Wander

Resolution: fixed
Status: newclosed

(In [1250]) * deactivated plugin validation (closes #138)

  • replaced some dll refs with project refs
  • new bins

comment:2 Changed 12 years ago by Matthäus Wander

(In [1251]) removed now obsolete workaround (references #138)

comment:3 Changed 10 years ago by Matthäus Wander

Milestone: CrypTool 2.0 RELEASE
Note: See TracTickets for help on using tickets.