[ orm-Bugs-1584744 ] CTP10 - ORM Reading Editor

[SourceForge.net <no...@so...>]

Bugs item #1584744, was opened at 2006-10-25 14:48
Message generated for change (Comment added) made by mcurland
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=809608&aid=1584744&group_id=158881

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Misc
Group: None
Status: Open
Resolution: Accepted
Priority: 6
Private: No
Submitted By: DBarden (dbarden)
Assigned to: Nobody/Anonymous (nobody)
Summary: CTP10 - ORM Reading Editor 

Initial Comment:
The ORM Reading Editor seems to 'go blank' after a 
bit of work.  If you click in empty space where some 
of the Reading Editor objects ought to be then they 
show up.

----------------------------------------------------------------------

>Comment By: Matthew Curland (mcurland)
Date: 2006-11-15 23:27

Message:
Logged In: YES 
user_id=1452263
Originator: NO

This is a symptom of a larger issue that the NORMA team is begining to
work through. As we add more toolwindows to NORMA we continue to add
additional DSLTools event listeners. One of them is causing problems, but
we don't know which one because we aren't seeing other error messages
associated with this report. Basically, an exception is causing event
firing to terminate prematurely, so some of our tool windows are getting
an ElementEventsBegun event but not an ElementEventsEnded. This
essentially leaves the grid-based windows (Reading, Reference Mode, Sample
Population) with redraw turned off and no way to turn it back on. Another
symptom is that a file reload wil give a whole bunch of duplicate name
errors (the name tracking also relies on the event sequence completing).
Basically, once you get in this state you should restart.

We are designing a mechanism to wrap individual event handlers so that
exceptions are isolated and do not cause system breakdowns. We will
include this with the next drop. That will also let use track what the
current underlying problem is (we don't actually know, this type of bug is
just a symptom).

A possible culprit (due to its youth and difficulty) is the ORM Context
Window. Close the tab, shut down VS, and restart to run without
initializing it.

----------------------------------------------------------------------

Comment By: Kevin M. Owen (kevinowen)
Date: 2006-11-11 21:38

Message:
Logged In: YES 
user_id=1014759

Thank you for reporting this problem. We have been able to reproduce it,
and are trying to work out exactly what is causing it.

----------------------------------------------------------------------

Comment By: Clifford Heath (cjheath)
Date: 2006-11-11 17:36

Message:
Logged In: YES 
user_id=1608419

Sorry, I should have read the rest of the bugs list before
commenting. It looks like my problem was described by
1441085, VS needing a restart - it seems to work OK now.

----------------------------------------------------------------------

Comment By: Clifford Heath (cjheath)
Date: 2006-11-11 17:24

Message:
Logged In: YES 
user_id=1608419

I have this problem in spades. The reading editor never
displays correctly, only maybe one time in ten displays
anything at all, and only some of those times is it possible
to enter the reading text. So it can take more than a minute
of clicking around before you can get to enter a single
reading - frustrating! It's all but completely broken.
Windows Server 2003 running under VMWare.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=809608&aid=1584744&group_id=158881