Trouble with 2017 command functionality

[JEdwardL]

Is there a reason that the functionality of ListBox_GetItemText was changed?

In previous versions a NIL value for this command was allowed and my routines were coded accordingly.  Previous to version 8.1 a NIL value passed to this command was allowed, but 8.1 throws an error message:  Error: NIL value not allowed

This causes a major problem because we're involved in a migration to AutoCAD 2017 which needs OpenDCL version 8.1 in order to run.  Unfortunately all of my code was written for version 8.0 which allowed the null value.  My code accepts NIL as a valid value and processes data accordingly. 

I'm not even sure that this is the only command that will throw a new error.  What other surprises are awaiting me?  Nobody is going to pay me to re-write all my code so it looks like we're stuck on AutoCAD 2014 until you guys fix this.

Thank you for your efforts.

[owenwengerd]

That function never accepted a NIL argument as far as I know. You've probably made some mistake in your testing.

[JEdwardL]

I don't know if it was designed to accept nil or not...all I know is that my code ran properly before with a nil value and it doesn't now.  I've commented out all references to ListBox_GetItemText and the code runs fine, but without some of the data that I was hoping to collect.

I've got another problem with Form_Close.  I noticed that you've changed the command to Form-Close, but the old syntax appears to still work.  I'm having trouble with the status code of Form-Close not being returned to Form-Show properly.  The status is returned properly for all of the controls except for the OK button which, after storing all of the desired values, closes the form and provide the proper code to Form-Show in order to terminate the WHILE loop I'm operating in.  I close the form with DCL-FORM-CLOSE INTERSECT_MAIN 1, which used returned status 1 to DCL_FORM_SHOW which set a flag to terminate the loop and iunload the project...everything was great it was one of my most-used routines.  But now I find that the status that is returned by the Form-Close command is the same status that was returned for closing the form for the previous control.

Something's screwy here or I'm missing something.  What could it be?

[Peter2]

It is easier to understand your problem if you post some code-snippets which show the behaviour.