id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
5682	Provide information about wrong graphical annotations when checking models in OMEdit	Francesco Casella	Adrian Pop	"Some time ago, we decided to suppress a lot of warnings issued by OMC when interacting with OMEdit, that were really confusing for end-users, who just saw lots of issues without having any means to understand them, let alone fix them. See #5048.

I think this is the correct approach from an end-user perspective.

Hoever, @lochel correctly pointed out that, in his role of library developer, he does not get any error message regarding wrong graphical annotations, which however has serious consequences (-> wrong diagram displayed). 

This is demonstrated by the attached model, which has a wrong annotation ({{{exxtent}}} is misspelled). This has a consequence on the displayed diagram (which uses the default extent instead), but there is no way to have OMEdit report where the problem is.

We agreed that the best solution is that those messages are normally suppressed, but are indeed shown when the model is ''checked''. I'm not sure if this should be done by the frontend, or if rather some extra API call should be performed after checking, without suppressing the output. 

@adeas31, can you please take care of that?"	defect	assigned	critical		Interactive Environment				Lennart Ochel Per Östlund