BreakPoint

cancel
Showing results for 
Search instead for 
Did you mean: 

I like TiTou's new signature! :^)

You are being very grumpySmiley Very Happy

but I with on the defer decision. What are the guys in NI (labview development team) reading!

What was wrong with the previous version options?

Regards

Ray Farmer (not grumpy like TiTou just puzzled)

Regards
Ray Farmer
Message 31 of 85
(5,719 Views)
Bearing in mind I have only got LV 6.1 to work with....

Could the "defer decision" save the changes to the VI you're working on, but not update references within the project to use the changed VI?  Basically saving it under a different name?

I dunno, it sounds wierd to me too.  When's LV 8.21 due out?  All these bugs seem to have a very soothing effect on me.  I normally am itching to upgrade to get all the new features.  But when upgrading includes getting all the new bugs, then I suddenly feel happier with 6.1.....

Shane.
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
Message 32 of 85
(5,712 Views)
there is a different way to do this

File >> Save as, and you get this :



This is a cool new feature I think

Message Edité par TiTou le 09-20-2006 10:53 AM


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

0 Kudos
Message 33 of 85
(5,709 Views)

TiTou

I get what you are saying. I use Defer Decision to make some trial changes to a SubVI without committing a save to disk until I am ready too.

Maybe the Save Changes dialog should also present a Revert button to remove the Cancel, Revert and Close procedure. Presenting a Revert button could lead to changes to a subvi being accidently lost if we are not careful...

I have to put my hand up and say I didn't know about Revert to force a reload from disk to memory, so thanks for that. Always learning ...

David 

Message 34 of 85
(5,702 Views)
David,

does this equate to "defer" just closing the front panel, keeping the VI in memory and not saving it?

Hmmm, interesting option.  You'd think these kind of changes would be explained well.  They're kind of central to LV usage.

Shane.
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
0 Kudos
Message 35 of 85
(5,697 Views)

The way I understand it (and mind you, I'm not an 8 user) the Defer Decision button is equivalent to the Don't Save button in previous versions.

What would happen is that if you would change a VI and it would stay in memory after you close its FP (if it was copied to the clipboard or if it is called by another VI in memory) then you would get a dialog with 4 options (Save, Don't, Explain Changes and Cancel Close).
Cancel wasn't always enabled (I don't know why), but essentially, "Defer Decision" is more accurate than "Don't Save" since if you clicked Don't Save the decision was simply defered until the next time you chose to remove the VI from memory (like when you removed its calling VI).

The behavior is exactly the same, only the wording is different.


___________________
Try to take over the world!
0 Kudos
Message 36 of 85
(5,712 Views)
There was also a thread on the LAVA forums with some more details on this (including NI explanations).

___________________
Try to take over the world!
0 Kudos
Message 37 of 85
(5,711 Views)

@Shane: Yes, thats right.

I agree with Tst that is a more accurate statement than Don't Save.

0 Kudos
Message 38 of 85
(5,712 Views)
True, true,

That's exactly what "don't save" did all along.  I missed that.

I also think it's less misleading that "don't save" since "don't save" suggests discarding changes.

Shane.
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
0 Kudos
Message 39 of 85
(5,711 Views)

Remind me ( as I dont have LabVIEW to hand), when you final unload that VI from memory, what options does it come up with if you still dont what to save the changes?

Ray.

Regards
Ray Farmer
0 Kudos
Message 40 of 85
(5,710 Views)