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



Eric,

I was able to reproduce the error using another member that was open in my
workspace when I upgraded to 8.0.3. I will send the details and screen
shots directly to you.

jon


date: Tue, 8 Nov 2011 17:55:20 -0500
from: Eric Chan <emchan@xxxxxxxxxx>
subject: Re: [WDSCI-L] Member name issue in RDP 8.0.3

Hey Jon, I'm seeing the escaping of the underscores now as well when I try
it. I'll look some more into it.

I couldn't reproduce the save error for a source member with an underscore
though. It seemed to save ok on my end, despite showing the name weirdly
in the title bar. Does this happen for you every time on a save?

Eric Chan
Rational Developer for Power
IBM Toronto Software Lab




From:
"jon" <joneverton@xxxxxxxxx>
To:
<wdsci-l@xxxxxxxxxxxx>
Date:
11/08/2011 01:59 PM
Subject:
[WDSCI-L] Member name issue in RDP 8.0.3
Sent by:
wdsci-l-bounces@xxxxxxxxxxxx



I have noticed since updating to 8.0.3 that RDP has an issue with
underscores in member names, M_CTL_RUN becomes M_5FCTL_5FRUN wherever the
member name is displayed. For what it's worth, hex '5F' is an ASCII
underscore. The only real issue this caused was trying to save the member
that I had open when I updated to 8.0.3 and RDP blew up when I tried to
save
after changing the member, probably something to do with source physical
files not liking member names longer than 10 bytes.

Jon Everton
Sr. Programmer/Analyst
Vertex Business Services



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.