Interesting...
I toggle to another perspective, and that source member has blanks tab saying "xxxx/xxxxx/xxxx.... does not exist." Where the XXX/XXXX/XXXX is the path of where the source was downloaded on my PC...
So, it appears that I had the source open another "perspective", and the editor got "hosed". (When I switched to debug...)
I close that tab, and then I was able to re-open the member...
So, maybe this error is created by having on perspective open with "dual panes", and then switching to debug. And then it tries to open that second "tab". And it "loses" the pointer to that second pane...
I ASSUME. JUST A GUESS...
I often do a lot of switching between "Perspectives" to do different actions, and that could by why I run into some "flaky" behavior...
Just a thought to share...
PS. Tried to duplicate, but switch perspective, the dual panes remained open. So, sadly, I am still unable to duplicate this "flaky" behavior. Darn! I thought I might have finally found a way to duplicate the error. But, failed at that again... <frown>
-Ken Killian-
-----Original Message-----
From: Ken Killian
Sent: Monday, September 14, 2015 3:15 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: RDi 9.1.1.1. Editor could not be initialized in DEBUG--> until RESTART/REBOOT RDI 9.1.1.1
Hi,
I tried to debug a very simpler "tester" program. Which RDI 9.1.1.1 is unable to open the source, that I just had open.
In the Error-Log, I get two messages repeated:
"unable to create part"
"Editor could not be initialized."
Here are some of the previous errors:
Uncaught exception in class "com.ibm.etools.iseries.parsers.ISeriesEditorRPGILEParser".
Live RPG parsing thread killed
An internal error occurred during: "Launching RemoteSystemsTempFiles".
Short video, just to prove it. (approx. 20-seconds)
https://picasaweb.google.com/102276967488806647195/RDI9111ErrorImages#6194421318387114850
Tinyurl:
http://tinyurl.com/onu8yn4
The debugger could not open the source. The open a member would also NOT work either.
The only interesting thing to note is that originally I had two windows open to copy source from production to a "Test-Program", to test a small piece of logic. I *THINK*/*ASSUME* that RDi 9.1.1.1 lost the pointer to different source pane. Just a guess! I DO NOT KNOW.
As usual, the restart clears the memory, and then RDI 9.1.1.1 works fine again.
Just annoying I guess. Probably nothing can be done, since my attempts to recreate this error have been unsuccessful.
-Ken Killian-
midrange.com
