id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
4598	OMEdit should not hang for more than a few seconds	Francesco Casella	Adeel Asghar	"A typical end-user experience when using OMEdit is that some action is initiated via the GUI, the pointer turns into an hourglass for a long (sometimes very long) time, without any possibility of interaction and without any feedback. This is quite annoying and gives a general impression of lousiness of the tool, as one has no idea if and when he/she will be back in control.

For operations involving the browsing of libraries and the graphical building of models by dragging and dropping, the problem is well-known, see #2960, and it should hopefully be solved by the new API based on the new front-end, which is expected to be one order of magnitude faster or more.

For operations like starting a simulation, however, the availability of the new front end will not be enough. There are reasonable and not particularly large end-user models that can take one or two minutes for flattening, back-end processing and code generation. During this time, the end-user should continuously get feedback about what is going on, as well as be allowed to do other things with OMEdit that do not involve the current simulation, e.g., browsing simulation results or other Modelica models. No more hourglass, please :)

In particular, the ""Compilation"" tab of the simulation output windows should report at least the main milestones of the code generation, such as those that you can get out of -d=exectstat, see also #3565 and the discussion therein.

It could also be nice if the bottom slice of the OMEdit window, which contains the Modelling, Plotting and Debugging tab selectors, also showed some indication of the CPU and disk activity of the OMEdit process and of its children, which can be very resource-intensive, as we all know. In this way, one gets a feeling that OMEdit is doing something and is not simply stuck. On Windows, I always run the Task Manager for this purpose, and htop on Linux, but that's not something that the newbie user would do, and it's not particularly user-friendly anyway.

Last, but not least, it should be possible to abort the compilation of a model anytime, also during the first phases such as flattening. If one accidentally starts a very lengthy compilation it makes no sense that he/she needs to wait forever for it to be finished, or, even worse, to kill the OMEdit process, restart it, and reload all the libraries and all the simulation results manually.

IMO, this feature is really needed to convey a professional feeling of the OMEdit GUI, so we should aim at getting it for 2.0.0."	defect	new	blocker	2.0.0	OMEdit				Andrea Bartolini massimo ceraolo alberto.leva@… omusability@…