Better diagnostics (for MDG)

[qwerty]

Whenever I create a MDG and make a mistake, some things simply do not work. No message. No trace. No hint. I have to start RPG (an once famous programming language; in Germany the acronym translates Rate, Probiere, Gucke - guess, experiment, look - maybe Riddle, Probe, Glance could be an equivalent acronym).

q.

(I'd wish the same for other secret things like e.g. XMI import with Duplicate Key messages, DB access errors in various circumstance. But MDG improvements would be a place to start with.)

[qwerty]

This really drives me crazy. A single diagram (Custom/Requirements) does not show the toolbox, but that of the standard requirement. It's probably a simple typo somewhere. But this scrappy system does not tell me anything.

- I'm Vader. shhhh.  Darth Vader. shhh. I can kill me with a single thought.

- oh s_h_i_t !!!  I killed myself

http://www.youtube.com/watch?v=Sv5iEK-IEzw

q.

[qwerty]

Nothing to say?

q.