You might want to check the workspace error log and see if you have an
error like "A handler conflict occurred. This may disable some
commands."
(In 8.5 it's at: Window->Show View->Other -> General -> Error Log)
I've had similar issues multiple times while going between the XML
editor and the RPG lpex editor. The only error I could find was the
handler conflict. In 8.5 it usually caused me to lose some features line
auto complete and "Enter" for new lines in lpex. In the XML editor it
caused enter to stop working at all.
I usually had to restart RDP to get the features back. Sometimes
reopening the source member would also work.
It got so bad in 8.5 that I went back to 8.0 to edit xml documents.
I have not installed 9.0 yet to see if it also has the issue.
I was unable to create a PMR since I don't have access. IBM should
really consider allowing registered users to create PMRs just so that
they can have some sort of record of the issue. Requiring the Company to
authorize the user in order to enter a bug report seems a little
extreme.
Chris Hiebert
Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the
author and do not necessarily represent those of the company.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Anderson, Kurt
Sent: Thursday, June 20, 2013 11:27 AM
To: Rational Developer for IBM i / Websphere Development Studio Client
forSystem i & iSeries
Subject: Re: [WDSCI-L] RDI v9.0 and LPEX Text Find
Looks like this may have been a symptom of another issue. I eventually
couldn't press enter to get a new line and had to re-open the source.
After reading your email, I tried Find again and see that it works as
expected. I'll have to figure out what caused the issue and report it.
Thanks,
Kurt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.