× 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.



Steve,

I have Create PMR# 03957,442,000 RDI should show if breakpoints are disabled

Problem description and business impact RDI should show if breakpoints are disabled. Whether breakpoints are disable by a single breakpoint or all.

I have also create PMR# 03958,442,000 RDI should ALWAYS show breakpoints if toggle between *LISTING/*SOURCE views

Problem description and business impact in 5250 debug, when toggling between *LISTING/*SOURCE view. I *ALWAYS* see the breakpoints WITHOUT FAIL! <Joy Joy> RDI should work the same way! I should be able to *ALWAYS* see the breakpoints in the User Interface. I can seem them on the view: Breakpoints. But the user interface does not show them. I can click to run until break-point. And I do NOT see the breakpoint in the source View! Ouch! Even though I see the breakpoints in the view breakpoints. Very strange. Why wouldn't the Breakpoints ALWAYS be visible??? That is an User-Interface failure. Please Fix.

Additional comments I "CANNOT" always see the icon for the break-points when toggling between *SOURCE/*LISTING views. Very Perplexing.



-Ken Killian-


-----Original Message-----
From: Ken Killian
Sent: Thursday, January 10, 2019 4:04 PM
To: 'Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries' <wdsci-l@xxxxxxxxxxxxxxxxxx>; Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Cc: Steve Ferrell <Steve.Ferrell@xxxxxxxxxxxxxxx>
Subject: RE: RDI 9.6.0.5 Disable break-points not showing as "Grey-Out" when status is *DISABLED* <Sad>

Steve,

I will open a PMR# on this tomorrow.

ON Visual Studio, the active break-point is RED, and an disable breakpoint is GREY. But, I know that RDI is limited by Eclipse.

Thanks again!


-Ken Killian-


-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steve Ferrell via WDSCI-L
Sent: Thursday, January 10, 2019 3:45 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>; Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Cc: Steve Ferrell <Steve.Ferrell@xxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDI 9.6.0.5 Disable break-points not showing as "Grey-Out" when status is *DISABLED* <Sad>

Hi Ken,

I'd suggest entering a PMR.

New behavior should be entered as an RFE. Bad UI design is a defect, and therefore a PMR.

Eclipse standard (just like the skip all breakpoints icon) is to disable and strike though. I'd prefer to see RDi change to use this same standard.

Thanks for helping make RDi better!

Steve Ferrell


-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Ken Killian
Sent: Thursday, January 10, 2019 2:21 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] RDI 9.6.0.5 Disable break-points not showing as "Grey-Out" when status is *DISABLED* <Sad>

Hi,

I am running into a debug break-point annoyance. Bad UI design.

So, we have two options with Break-Points:
* Enable (bright colors, because it is ACTIVE)
* Disable (Grayed out colors, because it is DISABLE) <thumbs up!> Good UI!

But if you clicked on the button: "Skip All Break Points" or shortcut (Ctrl+Alt+B).

All the break points show as *ENABLED* (bright). Bad UI design!

I checked with My Microsoft Co-workers, and VS Studio ALWAYS show their break-points "grayed-out". If you select "Disable all break Points". Or if you disable them individual. Unlike RDI. <RDi failure>

Microsoft Visual Studio IDE *ALWAYS* show the status of the break points! <Bravo!>

Another note on break-points UI in RDi.

If you toggle between *LISTING *SOURCE view, you do *NOT* always see all your set breakpoints. Depending where they were set. Either in *LISTING or *SOURCE view. Toggle between views does not refresh the "painting" of break-points. <disappointment>

On the plus-Side 5250 debug *ALWAYS* shows all break-points properly (Enable/Disable)! No MATTER what view you toggle.

Do I have open a PMR to get this functionality to work properly? Or is this RFE, because that would be an "Enhancement". Since the original design of the UI seems poor. <Puzzled-Look>

Once again, time wasted, due to bad UI.

-Ken Killian-


--
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.