Error while control update

[Unk]

I have a problem.

I have a large project and I need to modify it.

I want to add some elements to control (Strict Type Def.). My control - it is a cluster with numbers (or arrays).

But I can't to do it. When I want to save a new (modify) control, it appears a error:

**** (I don't remember)

allocsup.cpp (!!!)

and crush.

What I may to do for modify a control?

Thank you.

Message Edited by Unk on 08-07-2006 09:50 AM

[Wiebe@CARYA]

"Unk" <x@no.email> wrote in message news:1154931007660-400888@exchange.ni.com...
I have a problem.
I have a large project and I need to modify it.
I want to add some elements to control (Strict Type Def.). My control - it is a cluster with numbers (or arrays).
But I can't to do it. When I want to save a new (modify) control, it appears a error:
&nbsp;
**** (I don't remember)
allocsup.cpp (!!!)
&nbsp;
and crush.
&nbsp;
What I may to do for modify a control?
Thank you.Message Edited by Unk on 08-07-2006 09:50 AM



LabVIEW gets confused sometimes when you edit type defs, or strict type defs. Especially when you use type defs in another (clustered) type def.


Sometimes the only way to get around this is to close everything, make a new control and save it over the old one. When you make a new one, save occasionally and backup the saved version. If you get a crash (not a crush) you don't have to start all over again.


If you get a crash each to you make a change, try to change the order in which you do the changes.


Hope it helps.


Regards,


Wiebe.

[Unk]

Thank you, Wiebe@CARYA.

But your advice doesn't help me. It still crash. I don't know what to do.

Message Edited by Unk on 08-14-2006 08:46 AM

[tbd]

Hi Unk,

      I agree with Wiebe, types within types can be a pain when editing an "inner" type,  though I've never attributed a crash to this - just broken-arrows.

If I were you I'd do a mass-compile (Tools/Advanced) of everything associated with the type.  If that doesn't fix the problem, try to recreate the problem with a small set of VIs - saved as a LLB and posted here.

Also, an easy experiment would be to open the top-level type-def then do a "save-with-options" (File menu) to pull-together any/all member type-defs.  Perhaps the problem is a missing or broken member-type-def.  If the save is successful, close/open LabVIEW and see if you can modify the top-level type-def in its new (temporary) location.

Just some ideas