Sort of along the same line... (Maybe?)
A newbie complained to me that the RDi 9.0.1. is not allowing him to save member-source. He had to save to a new member name and then later rename it. He said what a pain.
I had to tell the newbie that RDi 9.0.1 is "FLAKY", and greys out the save-icon. It is a "Known Issue".
<Big Frown>
I also have issues with the right-click Context menu not popping up with all options. I have to do it second time for it to give me all the options. Hit Esc, and then do a re-try...
I also have to click on another tab to get the compiler menu to show up. I haven't had this issue with previous version of LPEX.
Oh well, I hope this if fixed on RDi 9.1, due to be released on May 23rd.
I have created a new work space, and I still have this "Flaky Repaint Issue"...
<frown>
Too bad, only 1/3 of the developers here use RDi. Because they over hear about "flaky" issues... It is too bad, they are afraid to even try it...
PS. It still beats SEU by a LOT!!!
<Big Smile>
-Ken Killian-
Over 8 years of using RSE/LPEX.
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Young
Sent: Monday, May 19, 2014 9:40 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDi not saving changes back to system
Well,
The problem appears to have corrected itself (for now).
I had to edit the same source member today, and everything is working fine.
Just for the record, I was the only one editing the source member at the time, and did not attempt to edit it in SEU.
The only reason I went into SEU (after I closed the edit session for the member in RDi) was that I was getting undefined field errors on the compile, and the field name it was referring to did not exist in the source. I had that name earlier, but changed it and that is when I started noticing that my changes were not being saved to the original source file.
Thanks for all the suggestions, and if it occurs again, I will try them.
Jeff Young
Sr. Programmer Analyst
On Sat, May 17, 2014 at 4:08 PM, Gerald Kern <jp2558@xxxxxxxxx> wrote:
I used to have that problem, but haven't for some time (knock, knock),
but one thing I'm fairly certain that causes this behavior is doing
work in RDi, then myself or someone else touches the same member in
SEU, and if I don't refresh the object table, the situation you
describe happens. One thing I've learned to do is refresh the object table rather often.
Hope that helps.
--
Thanks, Jerry
Gerald Kern - Information Technology
Programming Supervisor
IBM Certified RPG IV Developer
Lotus Notes/Domino Administrator
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623
Phone 419-479-5535
--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post a
message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
midrange.com
