Open Object Rexx

Bugs item #1548944, was opened at 2006-08-30 09:17
Message generated for change (Settings changed) made by rexx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1548944&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: Installation
Group: v3.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Terry (rtconstant)
>Assigned to: Mark Hessling (rexx)
Summary: No GUID put into Windows registry for WSH

Initial Comment:
In short the problem is that ooRexx 3.1 is "not putting
its GUID into the registry (as scripting engines are
supposed to do)" for WSH.

I have pasted portions of emails to/from the RexxLa
forum below for a more detailed explanation.


My email to RexxLa: 

   I am using Windows XP sp2 and ooRexx 3.1.

   I use 4Nt from JP Software.

   The current problem has to do with running ooRexx
under the Windows Scripting Host (WSH).

   I have been using a command line like the following
for some time now using 4Nt ver 7.

     cscript.exe //e:"Object Rexx" //NoLogo wsh.rex

   I just played with 4Nt 8 beta. Ver 8 has a new
"script" command that should make working with ooRexx
under WSH a bit easier. I ran into a problem. I
reported the problem to Rex Conn, the main developer at
JP Software. I have pasted, below, the pertinent part
of his reply -- part of my email to him quoted first
and then his reply.

         If I enter the following command line:
              script /e"Object Rexx" Wsh.rexh
         then I get the following error:
              Error (SYS): Invalid class string


Rex Conn's reply to me (my original email to him):

     The problem is actually with Object Rexx; it's not
putting its GUID into the registry (as scripting
engines are supposed to do).  Instead, it's relying on
the GUID being embedded in XML code that CSCRIPT parses
to find the script code.  (4NT & SCRIPT do not support
the XML code parsing; they expect to simply find the
executable code in the file.)


My question to RexxLa forum:

   Is Rex Conn correct that ooRexx should be putting
its GUID into the registry and is he accurate that
ooRexx does not so do?


Mark Hessling's reply to me:

Yes, Rex is probably correct. ooRexx does not add any
GUIDs to the registry for the WSH Engine.
Please raise a bug report on SourceForge.

Cheers, Mark


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1548944&group_id=119701

Bugs item #1548944, was opened at 2006-08-29 17:17
Message generated for change (Comment added) made by miesfeld
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1548944&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Installation
Group: v3.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Terry (rtconstant)
Assigned to: Mark Hessling (rexx)
Summary: No GUID put into Windows registry for WSH

Initial Comment:
In short the problem is that ooRexx 3.1 is "not putting
its GUID into the registry (as scripting engines are
supposed to do)" for WSH.

I have pasted portions of emails to/from the RexxLa
forum below for a more detailed explanation.


My email to RexxLa: 

   I am using Windows XP sp2 and ooRexx 3.1.

   I use 4Nt from JP Software.

   The current problem has to do with running ooRexx
under the Windows Scripting Host (WSH).

   I have been using a command line like the following
for some time now using 4Nt ver 7.

     cscript.exe //e:"Object Rexx" //NoLogo wsh.rex

   I just played with 4Nt 8 beta. Ver 8 has a new
"script" command that should make working with ooRexx
under WSH a bit easier. I ran into a problem. I
reported the problem to Rex Conn, the main developer at
JP Software. I have pasted, below, the pertinent part
of his reply -- part of my email to him quoted first
and then his reply.

         If I enter the following command line:
              script /e"Object Rexx" Wsh.rexh
         then I get the following error:
              Error (SYS): Invalid class string


Rex Conn's reply to me (my original email to him):

     The problem is actually with Object Rexx; it's not
putting its GUID into the registry (as scripting
engines are supposed to do).  Instead, it's relying on
the GUID being embedded in XML code that CSCRIPT parses
to find the script code.  (4NT & SCRIPT do not support
the XML code parsing; they expect to simply find the
executable code in the file.)


My question to RexxLa forum:

   Is Rex Conn correct that ooRexx should be putting
its GUID into the registry and is he accurate that
ooRexx does not so do?


Mark Hessling's reply to me:

Yes, Rex is probably correct. ooRexx does not add any
GUIDs to the registry for the WSH Engine.
Please raise a bug report on SourceForge.

Cheers, Mark


----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-30 16:26

Message:
Logged In: YES 
user_id=191588

Mark Hessling,

I looked into this a little bit.  Even though, in the 
install, ooRexx does not add any GUIDs to the registry, 
they are there.

I'm still in the learning state with this, but, I believe 
the Object Rexx Script engine is a "self-registering" COM 
object.

The ooRexx script engine GUID is: 13DAD011-B0C9-11D4-A829-
000629869785.  This is defined in: 
oorexx\platform\windows\orxscrpt\guids.hpp in the source.  
If you search for this in the registry you will find it.  
It is possible that you may need to actually run one of 
the samples that uses the ooRexx script engine before the 
entries get put in.

I installed ActiveState Perl, so I could compare the 
entries for PerlScript (which I know work from searching 
the web) and compared them to the ooRexx entries.  I'll 
attach a zip file containing the ooRexx entries and the 
PerlScript entries.

Basically, they look correct to me.  ooRexx seems to have 
all the same keys, etc.  The only thing I see is that 
under the CLSID entry, ooRexx is using 'Object Rexx' as 
the progid.  I don't think it is allowed to have a space 
in the ID.  (But, again I'm not 100% sure I understand the 
docs on OLE Automtation.)  

It could be that taking out the space would fix this - if 
it even is a real bug.  Maybe Terry can report this back 
to JP Software and see what they say.

I'll be happy to add this to the things I am looking 
into.  I can try taking out the space and recompiling the 
orxscrpt DLL, if Terry is willing to try it to see if it 
changes anything.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1548944&group_id=119701

Bugs item #1548944, was opened at 2006-08-29 17:17
Message generated for change (Comment added) made by miesfeld
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1548944&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Installation
Group: v3.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Terry (rtconstant)
Assigned to: Mark Hessling (rexx)
Summary: No GUID put into Windows registry for WSH

Initial Comment:
In short the problem is that ooRexx 3.1 is "not putting
its GUID into the registry (as scripting engines are
supposed to do)" for WSH.

I have pasted portions of emails to/from the RexxLa
forum below for a more detailed explanation.


My email to RexxLa: 

   I am using Windows XP sp2 and ooRexx 3.1.

   I use 4Nt from JP Software.

   The current problem has to do with running ooRexx
under the Windows Scripting Host (WSH).

   I have been using a command line like the following
for some time now using 4Nt ver 7.

     cscript.exe //e:"Object Rexx" //NoLogo wsh.rex

   I just played with 4Nt 8 beta. Ver 8 has a new
"script" command that should make working with ooRexx
under WSH a bit easier. I ran into a problem. I
reported the problem to Rex Conn, the main developer at
JP Software. I have pasted, below, the pertinent part
of his reply -- part of my email to him quoted first
and then his reply.

         If I enter the following command line:
              script /e"Object Rexx" Wsh.rexh
         then I get the following error:
              Error (SYS): Invalid class string


Rex Conn's reply to me (my original email to him):

     The problem is actually with Object Rexx; it's not
putting its GUID into the registry (as scripting
engines are supposed to do).  Instead, it's relying on
the GUID being embedded in XML code that CSCRIPT parses
to find the script code.  (4NT & SCRIPT do not support
the XML code parsing; they expect to simply find the
executable code in the file.)


My question to RexxLa forum:

   Is Rex Conn correct that ooRexx should be putting
its GUID into the registry and is he accurate that
ooRexx does not so do?


Mark Hessling's reply to me:

Yes, Rex is probably correct. ooRexx does not add any
GUIDs to the registry for the WSH Engine.
Please raise a bug report on SourceForge.

Cheers, Mark


----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-30 16:43

Message:
Logged In: YES 
user_id=191588

Well, looks like I can't attach a file.  Send me an e-mail 
if you would like to look at the registry entries I saved.

----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-30 16:26

Message:
Logged In: YES 
user_id=191588

Mark Hessling,

I looked into this a little bit.  Even though, in the 
install, ooRexx does not add any GUIDs to the registry, 
they are there.

I'm still in the learning state with this, but, I believe 
the Object Rexx Script engine is a "self-registering" COM 
object.

The ooRexx script engine GUID is: 13DAD011-B0C9-11D4-A829-
000629869785.  This is defined in: 
oorexx\platform\windows\orxscrpt\guids.hpp in the source.  
If you search for this in the registry you will find it.  
It is possible that you may need to actually run one of 
the samples that uses the ooRexx script engine before the 
entries get put in.

I installed ActiveState Perl, so I could compare the 
entries for PerlScript (which I know work from searching 
the web) and compared them to the ooRexx entries.  I'll 
attach a zip file containing the ooRexx entries and the 
PerlScript entries.

Basically, they look correct to me.  ooRexx seems to have 
all the same keys, etc.  The only thing I see is that 
under the CLSID entry, ooRexx is using 'Object Rexx' as 
the progid.  I don't think it is allowed to have a space 
in the ID.  (But, again I'm not 100% sure I understand the 
docs on OLE Automtation.)  

It could be that taking out the space would fix this - if 
it even is a real bug.  Maybe Terry can report this back 
to JP Software and see what they say.

I'll be happy to add this to the things I am looking 
into.  I can try taking out the space and recompiling the 
orxscrpt DLL, if Terry is willing to try it to see if it 
changes anything.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1548944&group_id=119701

Bugs item #1549561, was opened at 2006-08-30 13:28
Message generated for change (Comment added) made by cmslives
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1549561&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Interpreter
Group: v3.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Forrest Garnett (cmslives)
Assigned to: Nobody/Anonymous (nobody)
Summary: parse source output includes two bytes of trailing x'00'

Initial Comment:
PARSE SOURCE output includes two bytes of x'00'
trailing the program file name.

----------------------------------------------------------------------

>Comment By: Forrest Garnett (cmslives)
Date: 2006-08-30 13:44

Message:
Logged In: YES 
user_id=1587365

Bug observed on AIX 5.3, using ooRexx.rte 3.1.0.0 for AIX 5L
5.2 and 5.3, as well as ooRexx.rte 3.1.0.1 for AIX BETA2.   

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1549561&group_id=119701

Bugs item #1548628, was opened at 2006-08-29 10:54
Message generated for change (Comment added) made by bigrixx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1548628&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Installation
Group: None
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: ooRexx does not accept # as coment

Initial Comment:
Are there any way to include the character # ('23'x) as
a  comment character ? 

Thanks and regards.

----------------------------------------------------------------------

>Comment By: Rick McGuire (bigrixx)
Date: 2006-08-29 11:05

Message:
Logged In: YES 
user_id=1125291

There's nothing special about a '#' in a Rexx comment.  They
are allowed in comments.  Since the bug report creator did
not include any contact information or a sample
demonstrating the problem, this is being closed. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1548628&group_id=119701

Bugs item #1548628, was opened at 2006-08-30 00:54
Message generated for change (Comment added) made by rexx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1548628&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Installation
Group: None
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: ooRexx does not accept # as coment

Initial Comment:
Are there any way to include the character # ('23'x) as
a  comment character ? 

Thanks and regards.

----------------------------------------------------------------------

>Comment By: Mark Hessling (rexx)
Date: 2006-08-30 07:31

Message:
Logged In: YES 
user_id=86185

I think they mean as the character that begins a comment
line; like in shell scripts.
My answer is, if you can convince the ANSI Standards
Committee that the Rexx Standard should be changed to allow
# as the start of a comment character, then it can be
implemented.

----------------------------------------------------------------------

Comment By: Rick McGuire (bigrixx)
Date: 2006-08-30 01:05

Message:
Logged In: YES 
user_id=1125291

There's nothing special about a '#' in a Rexx comment.  They
are allowed in comments.  Since the bug report creator did
not include any contact information or a sample
demonstrating the problem, this is being closed. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1548628&group_id=119701

Bugs item #1546863, was opened at 2006-08-25 15:58
Message generated for change (Settings changed) made by bigrixx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1546863&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Classes
Group: v3.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Mark Miesfeld (miesfeld)
>Assigned to: Rick McGuire (bigrixx)
Summary: Access of null pointer in OLEObject getKnownMethods

Initial Comment:
Complete version information below, but it is ooRexx 
3.1.

In the getKnownMethods method of the OLEObject, the 
code accesses a possibly null pointer because the 
call to pTypeInfo->Release() is done outside of the 
section that does the check for a non-null pTypeInfo.

This causes the REXX interpretor to end abnormally.

This only happens if an object implementing the 
IDispatch interface returns 1 for GetTypeInfoCount 
and then does not return a TypeInfo pointer.

That the code is wrong can be seen through 
inspection.  

I've also included a test program that will 
illustrate the problem.  However, the test program 
will only illustrate the problem if the 
adbanner.adbanner ActiveX control is installed on the 
system.

I have a patch that I will provide.  My console 
output from the test program before the fix and after:

/* Unfixed OLEObject */

C:\work.ooRexx>getKnownMethodsCrash.rex

Creating an adbanner.adbanner object.
  This script ends by printing: Finished. to the 
console.  If you do not
  see "Finished" on the console the REXX process 
terminated abnormally.

Got the adbanner.adbanner object: an OLEOBJECT

C:\work.ooRexx>


/* Fixed OLEObject */

C:\work.ooRexx>getKnownMethodsCrash.rex

Creating an adbanner.adbanner object.
  This script ends by printing: Finished. to the 
console.  If you do not
  see "Finished" on the console the REXX process 
terminated abnormally.

Got the adbanner.adbanner object: an OLEOBJECT
No known methods for the object.
Finished.

C:\work.ooRexx>


C:\work.ooRexx>rexx -v
Open Object Rexx Interpreter Version3.1.0
Build date: Aug 15 2006
Copyright (c) IBM Corporation 1995, 2004.
Copyright (c) RexxLA 2005-2006.
All Rights Reserved.
This program and the accompanying materials
are made available under the terms of the Common 
Public License v1.0
which accompanies this distribution.
http://www.oorexx.org/license.html

C:\work.ooRexx>ver

Microsoft Windows XP [Version 5.1.2600]

C:\work.ooRexx>

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1546863&group_id=119701

Bugs item #1546863, was opened at 2006-08-25 15:58
Message generated for change (Settings changed) made by bigrixx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1546863&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Classes
Group: v3.1
>Status: Pending
>Resolution: Fixed
Priority: 5
Submitted By: Mark Miesfeld (miesfeld)
Assigned to: Rick McGuire (bigrixx)
Summary: Access of null pointer in OLEObject getKnownMethods

Initial Comment:
Complete version information below, but it is ooRexx 
3.1.

In the getKnownMethods method of the OLEObject, the 
code accesses a possibly null pointer because the 
call to pTypeInfo->Release() is done outside of the 
section that does the check for a non-null pTypeInfo.

This causes the REXX interpretor to end abnormally.

This only happens if an object implementing the 
IDispatch interface returns 1 for GetTypeInfoCount 
and then does not return a TypeInfo pointer.

That the code is wrong can be seen through 
inspection.  

I've also included a test program that will 
illustrate the problem.  However, the test program 
will only illustrate the problem if the 
adbanner.adbanner ActiveX control is installed on the 
system.

I have a patch that I will provide.  My console 
output from the test program before the fix and after:

/* Unfixed OLEObject */

C:\work.ooRexx>getKnownMethodsCrash.rex

Creating an adbanner.adbanner object.
  This script ends by printing: Finished. to the 
console.  If you do not
  see "Finished" on the console the REXX process 
terminated abnormally.

Got the adbanner.adbanner object: an OLEOBJECT

C:\work.ooRexx>


/* Fixed OLEObject */

C:\work.ooRexx>getKnownMethodsCrash.rex

Creating an adbanner.adbanner object.
  This script ends by printing: Finished. to the 
console.  If you do not
  see "Finished" on the console the REXX process 
terminated abnormally.

Got the adbanner.adbanner object: an OLEOBJECT
No known methods for the object.
Finished.

C:\work.ooRexx>


C:\work.ooRexx>rexx -v
Open Object Rexx Interpreter Version3.1.0
Build date: Aug 15 2006
Copyright (c) IBM Corporation 1995, 2004.
Copyright (c) RexxLA 2005-2006.
All Rights Reserved.
This program and the accompanying materials
are made available under the terms of the Common 
Public License v1.0
which accompanies this distribution.
http://www.oorexx.org/license.html

C:\work.ooRexx>ver

Microsoft Windows XP [Version 5.1.2600]

C:\work.ooRexx>

----------------------------------------------------------------------

>Comment By: Rick McGuire (bigrixx)
Date: 2006-08-29 06:39

Message:
Logged In: YES 
user_id=1125291

Thanks for contributing the fix!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1546863&group_id=119701

Bugs item #1547980, was opened at 2006-08-28 17:05
Message generated for change (Comment added) made by orexx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: Classes
Group: v3.1
Status: Open
Resolution: None
>Priority: 9
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Empty string not accepted as argument to OLE method

Initial Comment:
When an empty string is given as an argument to an OLE
method, the method fails with error message

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.

The errant behavior is exhibited by one of the ooRexx
sample programs: samples\ole\apps\samp05.rex.  E.g.
with ooRexx 3.1 on my Windows XP SP2 system:

  C:\progs\ooRexx\samples\ole\apps>samp05.rex
      53 *-*
WordProApp~NewDocument("AutomatedDocument.lwp","","default.mwp")
  Error 92 running
C:\progs\ooRexx\samples\ole\apps\samp05.rex line 53: 
OLE error

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.



Jon Hosking
jh910@...

----------------------------------------------------------------------

>Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 20:46

Message:
Logged In: YES 
user_id=662126

The same behaviour can be seen with the DHTML program for MS
Internet Explorer, which gets uploaded with this comment.
Merely press the "Hide" button when MSIE displays the HTML
text. 

Please note that it makes a difference whether one uses ""
or " " (a single blank). In the case of MSIE the app abends
in the case that a single blank is supplied in the DHTML
example.

As this bug can be really nasty with WSH/OLE ooRexx
applications (the same program may run and then bomb, if an
empty string is used), I temporarily increased the severity
level to the highest value and aks Rick et.al. to adjust the
level accordingly.

---rony


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Bugs item #1547980, was opened at 2006-08-28 17:05
Message generated for change (Comment added) made by orexx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Classes
Group: v3.1
Status: Open
Resolution: None
Priority: 9
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Empty string not accepted as argument to OLE method

Initial Comment:
When an empty string is given as an argument to an OLE
method, the method fails with error message

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.

The errant behavior is exhibited by one of the ooRexx
sample programs: samples\ole\apps\samp05.rex.  E.g.
with ooRexx 3.1 on my Windows XP SP2 system:

  C:\progs\ooRexx\samples\ole\apps>samp05.rex
      53 *-*
WordProApp~NewDocument("AutomatedDocument.lwp","","default.mwp")
  Error 92 running
C:\progs\ooRexx\samples\ole\apps\samp05.rex line 53: 
OLE error

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.



Jon Hosking
jh910@...

----------------------------------------------------------------------

>Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 21:09

Message:
Logged In: YES 
user_id=662126

Oops, mixed up the buttons on the DHTML example. One needs
to press the "Hide" button, which will set the value of the
style attribute "display" to the empty string.

---rony


----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 20:46

Message:
Logged In: YES 
user_id=662126

The same behaviour can be seen with the DHTML program for MS
Internet Explorer, which gets uploaded with this comment.
Merely press the "Hide" button when MSIE displays the HTML
text. 

Please note that it makes a difference whether one uses ""
or " " (a single blank). In the case of MSIE the app abends
in the case that a single blank is supplied in the DHTML
example.

As this bug can be really nasty with WSH/OLE ooRexx
applications (the same program may run and then bomb, if an
empty string is used), I temporarily increased the severity
level to the highest value and aks Rick et.al. to adjust the
level accordingly.

---rony


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Bugs item #1547980, was opened at 2006-08-28 17:05
Message generated for change (Comment added) made by orexx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Classes
Group: v3.1
Status: Open
Resolution: None
Priority: 9
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Empty string not accepted as argument to OLE method

Initial Comment:
When an empty string is given as an argument to an OLE
method, the method fails with error message

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.

The errant behavior is exhibited by one of the ooRexx
sample programs: samples\ole\apps\samp05.rex.  E.g.
with ooRexx 3.1 on my Windows XP SP2 system:

  C:\progs\ooRexx\samples\ole\apps>samp05.rex
      53 *-*
WordProApp~NewDocument("AutomatedDocument.lwp","","default.mwp")
  Error 92 running
C:\progs\ooRexx\samples\ole\apps\samp05.rex line 53: 
OLE error

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.



Jon Hosking
jh910@...

----------------------------------------------------------------------

>Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 21:57

Message:
Logged In: YES 
user_id=662126

O.K., I give in, some gremlins typing the name of the wrong
button: it should be the "unhide" button that assigns the
empty string to the display-attribute in the style element.
Sorry for this noise level...

---rony


----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 21:09

Message:
Logged In: YES 
user_id=662126

Oops, mixed up the buttons on the DHTML example. One needs
to press the "Hide" button, which will set the value of the
style attribute "display" to the empty string.

---rony


----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 20:46

Message:
Logged In: YES 
user_id=662126

The same behaviour can be seen with the DHTML program for MS
Internet Explorer, which gets uploaded with this comment.
Merely press the "Hide" button when MSIE displays the HTML
text. 

Please note that it makes a difference whether one uses ""
or " " (a single blank). In the case of MSIE the app abends
in the case that a single blank is supplied in the DHTML
example.

As this bug can be really nasty with WSH/OLE ooRexx
applications (the same program may run and then bomb, if an
empty string is used), I temporarily increased the severity
level to the highest value and aks Rick et.al. to adjust the
level accordingly.

---rony


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Bugs item #1547980, was opened at 2006-08-28 09:05
Message generated for change (Comment added) made by miesfeld
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Classes
Group: v3.1
Status: Open
Resolution: None
Priority: 9
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Empty string not accepted as argument to OLE method

Initial Comment:
When an empty string is given as an argument to an OLE
method, the method fails with error message

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.

The errant behavior is exhibited by one of the ooRexx
sample programs: samples\ole\apps\samp05.rex.  E.g.
with ooRexx 3.1 on my Windows XP SP2 system:

  C:\progs\ooRexx\samples\ole\apps>samp05.rex
      53 *-*
WordProApp~NewDocument("AutomatedDocument.lwp","","default.mwp")
  Error 92 running
C:\progs\ooRexx\samples\ole\apps\samp05.rex line 53: 
OLE error

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.



Jon Hosking
jh910@...

----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-28 17:55

Message:
Logged In: YES 
user_id=191588

I can reproduce this and I see in the code exactly where 
it is happening.

So, I should be able to come up with a fix in a day or 
two.  Or, if I don't have time during the work week, then 
this weekend.

----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 13:57

Message:
Logged In: YES 
user_id=662126

O.K., I give in, some gremlins typing the name of the wrong
button: it should be the "unhide" button that assigns the
empty string to the display-attribute in the style element.
Sorry for this noise level...

---rony


----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 13:09

Message:
Logged In: YES 
user_id=662126

Oops, mixed up the buttons on the DHTML example. One needs
to press the "Hide" button, which will set the value of the
style attribute "display" to the empty string.

---rony


----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 12:46

Message:
Logged In: YES 
user_id=662126

The same behaviour can be seen with the DHTML program for MS
Internet Explorer, which gets uploaded with this comment.
Merely press the "Hide" button when MSIE displays the HTML
text. 

Please note that it makes a difference whether one uses ""
or " " (a single blank). In the case of MSIE the app abends
in the case that a single blank is supplied in the DHTML
example.

As this bug can be really nasty with WSH/OLE ooRexx
applications (the same program may run and then bomb, if an
empty string is used), I temporarily increased the severity
level to the highest value and aks Rick et.al. to adjust the
level accordingly.

---rony


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Bugs item #1547980, was opened at 2006-08-28 09:05
Message generated for change (Comment added) made by miesfeld
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Classes
Group: v3.1
Status: Open
Resolution: None
Priority: 9
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Empty string not accepted as argument to OLE method

Initial Comment:
When an empty string is given as an argument to an OLE
method, the method fails with error message

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.

The errant behavior is exhibited by one of the ooRexx
sample programs: samples\ole\apps\samp05.rex.  E.g.
with ooRexx 3.1 on my Windows XP SP2 system:

  C:\progs\ooRexx\samples\ole\apps>samp05.rex
      53 *-*
WordProApp~NewDocument("AutomatedDocument.lwp","","default.mwp")
  Error 92 running
C:\progs\ooRexx\samples\ole\apps\samp05.rex line 53: 
OLE error

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.



Jon Hosking
jh910@...

----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-28 22:02

Message:
Logged In: YES 
user_id=191588

I have a fix for this bug and have submitted a patch.  
Patch # 1548311.

----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-28 17:55

Message:
Logged In: YES 
user_id=191588

I can reproduce this and I see in the code exactly where 
it is happening.

So, I should be able to come up with a fix in a day or 
two.  Or, if I don't have time during the work week, then 
this weekend.

----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 13:57

Message:
Logged In: YES 
user_id=662126

O.K., I give in, some gremlins typing the name of the wrong
button: it should be the "unhide" button that assigns the
empty string to the display-attribute in the style element.
Sorry for this noise level...

---rony


----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 13:09

Message:
Logged In: YES 
user_id=662126

Oops, mixed up the buttons on the DHTML example. One needs
to press the "Hide" button, which will set the value of the
style attribute "display" to the empty string.

---rony


----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 12:46

Message:
Logged In: YES 
user_id=662126

The same behaviour can be seen with the DHTML program for MS
Internet Explorer, which gets uploaded with this comment.
Merely press the "Hide" button when MSIE displays the HTML
text. 

Please note that it makes a difference whether one uses ""
or " " (a single blank). In the case of MSIE the app abends
in the case that a single blank is supplied in the DHTML
example.

As this bug can be really nasty with WSH/OLE ooRexx
applications (the same program may run and then bomb, if an
empty string is used), I temporarily increased the severity
level to the highest value and aks Rick et.al. to adjust the
level accordingly.

---rony


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Bugs item #1547980, was opened at 2006-08-28 09:05
Message generated for change (Comment added) made by miesfeld
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Classes
Group: v3.1
Status: Open
Resolution: None
Priority: 9
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Empty string not accepted as argument to OLE method

Initial Comment:
When an empty string is given as an argument to an OLE
method, the method fails with error message

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.

The errant behavior is exhibited by one of the ooRexx
sample programs: samples\ole\apps\samp05.rex.  E.g.
with ooRexx 3.1 on my Windows XP SP2 system:

  C:\progs\ooRexx\samples\ole\apps>samp05.rex
      53 *-*
WordProApp~NewDocument("AutomatedDocument.lwp","","default.mwp")
  Error 92 running
C:\progs\ooRexx\samples\ole\apps\samp05.rex line 53: 
OLE error

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.



Jon Hosking
jh910@...

----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-28 22:32

Message:
Logged In: YES 
user_id=191588

I have a fix for this bug and have submitted a patch.  
Patch # 1548311.

----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-28 22:02

Message:
Logged In: YES 
user_id=191588

I have a fix for this bug and have submitted a patch.  
Patch # 1548311.

----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-28 17:55

Message:
Logged In: YES 
user_id=191588

I can reproduce this and I see in the code exactly where 
it is happening.

So, I should be able to come up with a fix in a day or 
two.  Or, if I don't have time during the work week, then 
this weekend.

----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 13:57

Message:
Logged In: YES 
user_id=662126

O.K., I give in, some gremlins typing the name of the wrong
button: it should be the "unhide" button that assigns the
empty string to the display-attribute in the style element.
Sorry for this noise level...

---rony


----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 13:09

Message:
Logged In: YES 
user_id=662126

Oops, mixed up the buttons on the DHTML example. One needs
to press the "Hide" button, which will set the value of the
style attribute "display" to the empty string.

---rony


----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 12:46

Message:
Logged In: YES 
user_id=662126

The same behaviour can be seen with the DHTML program for MS
Internet Explorer, which gets uploaded with this comment.
Merely press the "Hide" button when MSIE displays the HTML
text. 

Please note that it makes a difference whether one uses ""
or " " (a single blank). In the case of MSIE the app abends
in the case that a single blank is supplied in the DHTML
example.

As this bug can be really nasty with WSH/OLE ooRexx
applications (the same program may run and then bomb, if an
empty string is used), I temporarily increased the severity
level to the highest value and aks Rick et.al. to adjust the
level accordingly.

---rony


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Bugs item #1547980, was opened at 2006-08-28 11:05
Message generated for change (Comment added) made by bigrixx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Classes
Group: v3.1
Status: Open
Resolution: None
Priority: 9
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Empty string not accepted as argument to OLE method

Initial Comment:
When an empty string is given as an argument to an OLE
method, the method fails with error message

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.

The errant behavior is exhibited by one of the ooRexx
sample programs: samples\ole\apps\samp05.rex.  E.g.
with ooRexx 3.1 on my Windows XP SP2 system:

  C:\progs\ooRexx\samples\ole\apps>samp05.rex
      53 *-*
WordProApp~NewDocument("AutomatedDocument.lwp","","default.mwp")
  Error 92 running
C:\progs\ooRexx\samples\ole\apps\samp05.rex line 53: 
OLE error

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.



Jon Hosking
jh910@...

----------------------------------------------------------------------

>Comment By: Rick McGuire (bigrixx)
Date: 2006-08-29 06:19

Message:
Logged In: YES 
user_id=1125291

Mark,

Thanks for the patch.  I'll try to get your patches
integrated today.  For future reference, you don't need to
open a new patch tracker item to submit patches for bugs. 
Just attach the patch to the original bug report.  This
makes the book keeping a little simpler.

Rick


----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-29 00:32

Message:
Logged In: YES 
user_id=191588

I have a fix for this bug and have submitted a patch.  
Patch # 1548311.

----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-29 00:02

Message:
Logged In: YES 
user_id=191588

I have a fix for this bug and have submitted a patch.  
Patch # 1548311.

----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-28 19:55

Message:
Logged In: YES 
user_id=191588

I can reproduce this and I see in the code exactly where 
it is happening.

So, I should be able to come up with a fix in a day or 
two.  Or, if I don't have time during the work week, then 
this weekend.

----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 15:57

Message:
Logged In: YES 
user_id=662126

O.K., I give in, some gremlins typing the name of the wrong
button: it should be the "unhide" button that assigns the
empty string to the display-attribute in the style element.
Sorry for this noise level...

---rony


----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 15:09

Message:
Logged In: YES 
user_id=662126

Oops, mixed up the buttons on the DHTML example. One needs
to press the "Hide" button, which will set the value of the
style attribute "display" to the empty string.

---rony


----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 14:46

Message:
Logged In: YES 
user_id=662126

The same behaviour can be seen with the DHTML program for MS
Internet Explorer, which gets uploaded with this comment.
Merely press the "Hide" button when MSIE displays the HTML
text. 

Please note that it makes a difference whether one uses ""
or " " (a single blank). In the case of MSIE the app abends
in the case that a single blank is supplied in the DHTML
example.

As this bug can be really nasty with WSH/OLE ooRexx
applications (the same program may run and then bomb, if an
empty string is used), I temporarily increased the severity
level to the highest value and aks Rick et.al. to adjust the
level accordingly.

---rony


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Bugs item #1547980, was opened at 2006-08-28 11:05
Message generated for change (Comment added) made by bigrixx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Classes
Group: v3.1
>Status: Pending
>Resolution: Fixed
Priority: 9
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Empty string not accepted as argument to OLE method

Initial Comment:
When an empty string is given as an argument to an OLE
method, the method fails with error message

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.

The errant behavior is exhibited by one of the ooRexx
sample programs: samples\ole\apps\samp05.rex.  E.g.
with ooRexx 3.1 on my Windows XP SP2 system:

  C:\progs\ooRexx\samples\ole\apps>samp05.rex
      53 *-*
WordProApp~NewDocument("AutomatedDocument.lwp","","default.mwp")
  Error 92 running
C:\progs\ooRexx\samples\ole\apps\samp05.rex line 53: 
OLE error

  Error 92.903:  Cannot convert REXX object to VARIANT:
The conversion of  into a VARIANT failed.



Jon Hosking
jh910@...

----------------------------------------------------------------------

>Comment By: Rick McGuire (bigrixx)
Date: 2006-08-29 06:39

Message:
Logged In: YES 
user_id=1125291

Applied.  Thanks for the contribution Mark. 

----------------------------------------------------------------------

Comment By: Rick McGuire (bigrixx)
Date: 2006-08-29 06:19

Message:
Logged In: YES 
user_id=1125291

Mark,

Thanks for the patch.  I'll try to get your patches
integrated today.  For future reference, you don't need to
open a new patch tracker item to submit patches for bugs. 
Just attach the patch to the original bug report.  This
makes the book keeping a little simpler.

Rick


----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-29 00:32

Message:
Logged In: YES 
user_id=191588

I have a fix for this bug and have submitted a patch.  
Patch # 1548311.

----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-29 00:02

Message:
Logged In: YES 
user_id=191588

I have a fix for this bug and have submitted a patch.  
Patch # 1548311.

----------------------------------------------------------------------

Comment By: Mark Miesfeld (miesfeld)
Date: 2006-08-28 19:55

Message:
Logged In: YES 
user_id=191588

I can reproduce this and I see in the code exactly where 
it is happening.

So, I should be able to come up with a fix in a day or 
two.  Or, if I don't have time during the work week, then 
this weekend.

----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 15:57

Message:
Logged In: YES 
user_id=662126

O.K., I give in, some gremlins typing the name of the wrong
button: it should be the "unhide" button that assigns the
empty string to the display-attribute in the style element.
Sorry for this noise level...

---rony


----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 15:09

Message:
Logged In: YES 
user_id=662126

Oops, mixed up the buttons on the DHTML example. One needs
to press the "Hide" button, which will set the value of the
style attribute "display" to the empty string.

---rony


----------------------------------------------------------------------

Comment By: Rony G. Flatscher (orexx)
Date: 2006-08-28 14:46

Message:
Logged In: YES 
user_id=662126

The same behaviour can be seen with the DHTML program for MS
Internet Explorer, which gets uploaded with this comment.
Merely press the "Hide" button when MSIE displays the HTML
text. 

Please note that it makes a difference whether one uses ""
or " " (a single blank). In the case of MSIE the app abends
in the case that a single blank is supplied in the DHTML
example.

As this bug can be really nasty with WSH/OLE ooRexx
applications (the same program may run and then bomb, if an
empty string is used), I temporarily increased the severity
level to the highest value and aks Rick et.al. to adjust the
level accordingly.

---rony


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1547980&group_id=119701

Bugs item #1546516, was opened at 2006-08-25 05:06
Message generated for change (Comment added) made by bigrixx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1546516&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Rick McGuire (bigrixx)
Assigned to: David Ashley (wdashley)
Summary: Fix description of stem default value.

Initial Comment:
The documentation for the stem class contains the
following statement:

     In addition to the items assigned to the
collection indexes,
     a stem also has a default value that is used for all
     uninitialized indexes of the collection.

This implies that the default value will be used for
explicitly dropped variables, rather than the value
created from the derived name.  This section needs to
be redone to match the documentation for stem variable
behavior. 

----------------------------------------------------------------------

>Comment By: Rick McGuire (bigrixx)
Date: 2006-08-25 05:20

Message:
Logged In: YES 
user_id=1125291

Suggested correction:
   creates a new stem collection with the name "A."
   and assigns it to the REXX variable A.;  it also assigns
   the value 2 to entry 1 in the collection.

The value of an uninitialied stem index is the stem object NAME
concatenated with the derived stem index.  For
example

   say a.[1,2]  -- implcitly creates stem object with name "A."
                -- displays "A.1.2"

   a = .stem~new("B.")
   say a[1,2]     -- displays "B.1.2"

In addition to the items explicitly assigned to the
collection indexes,
a value may be assigned to all possible stem indexes.  The
[]= method (with no index argument)
will assign the target value to all possible stem indexes. 
Following assignment,
a reference to any index will return the new value until
another value is assigned or the
index is dropped.

The [] method (with no index specified) will retrieve any
globally assigned value.  By default, this 
returns the stem NAME value. 



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1546516&group_id=119701

Bugs item #1544366, was opened at 2006-08-22 06:22
Message generated for change (Comment added) made by sahananda
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1544366&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Deleted
Resolution: None
Priority: 5
Submitted By: Jon Wolfers (sahananda)
Assigned to: Nobody/Anonymous (nobody)
Summary: OODialog Tree Control ItemInfo bug

Initial Comment:
3.0.0 WinXP

aTreeControl~ItemInfo returns a stem of values.

Possible returns for ItemInfo.!State are any
combination of [EXPANDED,BOLD,SELECTED,EXPANDEDONCE,INDROP]

ItemInfo.!State contains 'EXPANDED' when the item is
not expanded and does not contain it when the item is
expanded.

ItemInfo.!State appears to contain 'EXPANDEDONCE'
always whether the item has been expanded or not

The terms BOLD & SELECTED appear apropriately.  
I have not tested INDROP.

I will post a test script shortly.

thanks,

Jon

----------------------------------------------------------------------

>Comment By: Jon Wolfers (sahananda)
Date: 2006-08-25 07:14

Message:
Logged In: YES 
user_id=667060

Although this behaviour persists in my production code, I
cannot (and I have tried - beleive me) recreate the
behaviour in the testbed I produced which behaves exactly as
the manual suggests it should.

I therefore am attempting to close or delete this problem

Jon

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1544366&group_id=119701