× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 09/23/2019
05:54:49 PM:
----- Message from Ken Killian <kkillian@xxxxxxxxxxxx> on Mon, 23
Sep 2019 21:54:46 +0000 -----

To:

Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] Stored procedure SEP not stopping...

Thanks! Yes the debug icon does show. It just does not show the
disable status like eclipse. That is my only point.

Sadly, I have gotten burned by that several times. And thought I was
going crazy. It was just that the editor was not sowing the disable
status like Eclipse or visual studio.

The RDi team missed that when creating LPEX. . . .


No they did not miss it. Breakpoint icons are different when enabled and
when disabled.

https://imgur.com/a/w1HEOtI

You're not communicating clearly. From what I can tell, what you want is
one of two things

1) A different indication of disabled breakpoints. (i.e., Put a slash
through the breakpoint icon when disabled.)

2) The same indication on the individual breakpoints when the 'Skip All
Breakpoints' is selected.

Maybe you want both, I can't really tell. You'll need to be clear or you
won't be happy if IBM implements the wrong choice. I don't believe your
RFE is clear on this.

Michael Quigley
Computer Services
The Way International

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.