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



Within the last couple of days I have moved from the cozy world of WDSC 7.0 to the brave new world of RDP 7.6. So far my journey through this (with a little help from another colleague) has been smooth, and I have been able to get most everything working as before. However one area I continue to have some issues with is the Debug view.

While I have been able to successfully debug a few applications, the behavior is slightly different, and it might just be some set up issues. So here goes with my list of Debug issues...

-- When starting the debugger, there are several views available but it always seems to want to debug the program listing view. When it does that, the option that's checked to center the debug view doesn't work. How do I get it to consistently bring up the right view of the debugger so it does the centering correctly? Also, if it does bring up a view and I want to switch it while in debugging mode, how do I get to that setting? (It's similar to when it doesn't have the source available and presents you with three buttons to define where the source is, show the compiler listing, etc.)
-- Most of the time when stepping through lines of source code, it takes about 1/2 second for each step to occur (when pressing F5 or F6). Then there are the occasional bursts of speed that, if you're lucky, you go through 20 to 30 lines of code per second. How does this happen, and what settings affect this? (I'll have to see how the animated step feature works...)
-- Awhile back (in an earlier version of WDSC) when stepping through source, it also stepped through each line of an input or output file as well. It's not doing that in the later versions, which is OK, but there might be an occasion where I would want to step through those lines to validate some incoming information as it's being read in (e.g. hovering over the field names with the mouse, which I find convenient). Is there a setting change for this, or did IBM do away with these lines while stepping through your source?

Other things might come up as I fine tune this app, including whether or not a few observed quirks are now history in the new RDP. Thanks in advance for anyone's help/input/feedback.

Ken Tarr
Associated Banc Corp
Green Bay Service Center, Mail Stop 7055
2870 Holmgren Way
Green Bay, WI 54304
www.associatedbank.com


This e-mail and attachment(s) may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this message is strictly prohibited. If received in error, please notify the sender immediately and delete/destroy the message and any copies thereof. Although Associated Banc-Corp and/or its affiliates (collectively "Associated") attempt to prevent the passage of viruses via e-mail and attachments thereto, Associated does not guarantee that either are virus-free, and accepts no liability for any damage sustained as a result of any such viruses. Any federal tax advice contained in this communication (including any attachments) is not intended or written to be used or referred to in the promoting, marketing, or recommending of any entity, investment plan or agreement, nor is such advice intended or written to be used, and cannot be used, by a taxpayer for the purpose of avoiding penalties under the Internal Revenue Tax Code


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.