Error Mess: Cannot DEL transformation ??

[Dave Jochum]

5 minutes before a client is due in my office I find what I think is a duplicate slab in the section window. I delete it, and without saving (so I could just undo if necessary), view the model in 3D to make sure I didn't just trash something I wanted. (I was unsure, because in plan, selecting all did not show a duped slab.) As the 3D window script is running I get about 20 error messages like the one attached, but with different line numbers referenced. I went to undo, but it was greyed out. Just my luck I guess that an autosave had just taken place. It obviously refers to casement windows, none of which I touched in deleting the slab. Can a GDL guru out there tell me what this means and how to fix it?

TIA

[Anonymous]

This is an internal error in a GDL script. I can't imagine how deleting a slab could cause it. There should in fact be no way that a user's actions could cause this error. I have to wonder if it is some kind of corruption in the temp folder/building model. Quit & relaunch might fix it.

BTW the undo cue is not cleared by auto-save, but it is by a section window rebuild. VERY annoying and I really don't understand why

[Aussie John]

Ihave seen something like that and a restart cleared it up

[Dave Jochum]

Matthew wrote:
This is an internal error in a GDL script. I can't imagine how deleting a slab could cause it. There should in fact be no way that a user's actions could cause this error. I have to wonder if it is some kind of corruption in the temp folder/building model. Quit & relaunch might fix it.

Quitting and even rebooting didn't help. Selecting any casement window and then opening the parameters window also displays the error message. Arghhh! The windows display fine in all views--2D and 3D, however.

Matthew wrote:
BTW the undo cue is not cleared by auto-save, but it is by a section window rebuild. VERY annoying and I really don't understand why

Thanks--didn't know that. The lack of undo control is mindboggling. Even freeware drawing programs have better.

[Aussie John]

I know this might sound strange but open up the errant library part and resave it - reload library then see how it works

[Anonymous]

Oh, I should have mentioned that this particular error generally has no adverse effect on the display or modeling of the library part.

Try John's suggestion, and while you're at it push the "Check Scripts" button and see if you get any errors.

BTW, are they old (6.5/7.0) or new 8.0/8.1 windows? Are they from the latest 8.1 library or an earlier one?

[Aussie John]

I think you will find you the error is related to a specific combination of parameters. As such if you check the script you might not get the error.
Temporarily change the default parameters to match those in your model ( maybe better to create a duplicate window) then run your check scripts.

[Dave Jochum]

Matthew wrote:
Oh, I should have mentioned that this particular error generally has no adverse effect on the display or modeling of the library part.

No, that's true. They display fine. The problem is all the error messages popping up every time I draw a 3D or S/E window.

Matthew wrote:
Try John's suggestion, and while you're at it push the "Check Scripts" button and see if you get any errors.

I get a paragraph of errors when checking the script. Would it be any help to post the errors? When following John's suggestion, do I save the part over itself in the same library?

Matthew wrote:
BTW, are they old (6.5/7.0) or new 8.0/8.1 windows? Are they from the latest 8.1 library or an earlier one?

It's the 8.1 library, without the v2 update.

[Aussie John]

Dave wrote:
When following John's suggestion, do I save the part over itself in the same library?

I would recommend making a copy first then save over the original

[Dave Jochum]

Aussie wrote:
I know this might sound strange but open up the errant library part and resave it - reload library then see how it works

I tried this suggestion also to no avail. Merging into a new and reset PLN hasn't helped. Short of deleting and re-creating all the errant windows, I'm not sure what else to try.