I like TiTou's new signature! :^)

[Ben]

I just got an update from support.

"

Ben,
 I was able to see your issue on another computer. ...

"

Re: the perception that LV 8.20 is buggy...

Please keep in mind that the "Bug List" is very young in LV time. 8.0 was the first version to go through our public BUGrinder. 8.20 has a lot of bug fixes that include bugs that go back to LV 6.1. If no new things are introduced and we stay hot on reporting 8.20 bugs as soon as we find them, there is a potential that 8.20.1 will be as solid as LV 6.1 was.

Ben

[TiTou]

---

shoneill a écrit:

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.

---

Well... more or less... before LV8, for all the subVIs you closed and clicked "don't save" you had a "save subVI window" when closing the main VI.
Now just one window comes asking you to select subVIs you want to save in a list. And that list is as long as thenumber of subVIs with unsaved modifications... well done to those who will remember when they close

[shoneill]

Titou,

Isn't it so that each changed sub-vi came with it's owm dialog as to whether the changed should be saved?  Isn't the difference simply one dialog with many entries versus many dialog with single entries.

If you have a list of changed sub-vis in LV 6.1, then each one asks for saving before closing.  Of course it's possible to click "Yes to all", but that's similar to simply selecting all entries in LV 8.  Is this really a major difference?

Shane.

[Ray.R]

---

TiTou wrote:
It seems to me that NI hired a bunch developpers coming straight from Microsoft

---

Oooooooooohhhhhh!!

Now that's bad!!

But unfortunately a bit true!

Yes.  I saw that with LV8.20.  I hate to say this on an NI site, but that is .....  rediculous!!

What the heck is "Defer decision".  Give me "SAVE" & "CANCEL"  I'll figure out the rest.

I have similar beef with "SAVE AS".  Holy (something), you have to be careful with this one because if you pick the wrong one, you can save with a new name, but not have an extra copy.   I don't get it..  What's going on???  And when asking NI people how they came up with these changes, they tell us that they asked veteran users of LV on what features they should have... 

From the sounds of this thread, it appears to me that the veterans don't like those new features...  Am I wrong??

I really like working with LV7.1.  I can't say the same with LV8.x..

Maybe we're just a bunch of grumpy old men..  Including TiTou.. being the oldest of us all!!  😉

😄

======== EDIT ========

Wow..  there was already a whole new page of postings on this..  Just catching up on my reading..

Hummm..

Defer Decision..  OK.  Humm..  I don't know what to say.. 

It's just that using LV has become so much different than the previous (LV7.1) version that you just don't know what the heck they mean with these new choices...  for something as trivial as "SAVE" or "EXIT"..  What complicate things so much??  😐

I'll stop here...  And let TiTou continue... He's doing a good job... 😉

Message Edited by JoeLabView on 09-20-2006 09:42 AM

[TiTou]

---

shoneill a écrit:
Titou,

Isn't it so that each changed sub-vi came with it's owm dialog as to whether the changed should be saved?  Isn't the difference simply one dialog with many entries versus many dialog with single entries.

If you have a list of changed sub-vis in LV 6.1, then each one asks for saving before closing.  Of course it's possible to click "Yes to all", but that's similar to simply selecting all entries in LV 8.  Is this really a major difference?

Shane.

---

Well... I assume we all react differently to this because we don't work the same way... What I was used to do is to close subVIs and decide right away to save or not changes, so when at the end the dialog came I would say "don't save subVIs".
And the possibility to differ the save for when I close everything really seems useless to me ; but this because of the way I am used to work 😉

[DavidJCrawford]

@ Ray Farmer

This is what it looks like if you delete a changed subvi from memory

cheers

David

Message Edited by David Crawford on 09-20-2006 03:00 PM

[RayFarmer]

Isn't that the same as previous version?

[tst]

---

@TiTou wrote:

... What I was used to do is to close subVIs and decide right away to save or not changes, so when at the end the dialog came I would say "don't save subVIs".
And the possibility to differ the save for when I close everything really seems useless to me ; but this because of the way I am used to work 😉

---

But you can still do that. At least 8.2 (and I assume 8.0 as well) has a Don't Save - All button (if the check box under it is checked) which is functionally identical to Don't Save SubVIs.

I agree that Don't Save SubVIs is more easily understood (at least for us who know it), but Defer Decision is definitely more Accurate than the Don't Save we used to have since the VI (with its changes) was still in memory.

The problems I do have with the new dialog is that the Affected Items area is useless (The VIs are displayed in several columns, which is unreadable) and that
List Unsaved Changes is for some reason displayed as a hyperlink instead of button (what is that good for?). I think whoever wrote this window had the same feeling about the Items area because they supplied an option to hide it (the small triangle).

If you do actually click the "link", you will see that the Explain Changes dialog is not very useful either. I think that this should all be a single (resizable) dialog which would allow us to select all the items we want to save from the list and not to have perform the same function on all the VIs or on a single VI at a time.

[DavidJCrawford]

Ray, its this dialog that TiTou had a pop at.

These are the old Save Changes dialogs in 7.1 depending on whether you close the subvi or delete from memory.

cheers

David

Message Edited by David Crawford on 09-20-2006 03:26 PM

Message Edited by David Crawford on 09-20-2006 03:26 PM

[Ray.R]

Am I the only one confused by

Defer Decision:  Keep unsaved changes in memory

What the heck does that mean?  If I don't want to save it why would I want to keep unsaved changes in memory?  To do what?

I dunno... I'm confused..  Maybe it's a French thing..  Maybe TiTou & I should read it backwards..  😉

Tenir les changement non-sauvegarder en memoire...    hein???

Let's see... I don't want to save the last changes, and I want to close the VI..  What are my choices?

1.  Save   (I don't want to do this.  I want to discard my changes)

2.  Defer Decision  (Keep unsaved changes in memory.  I don't want to save any changes.  I simply want to close the vi or quit.. This sounds scary!)

3. Cancel  (Oh NO!!  After all this trouble... I'll be back at square one!... So.. I certainly don't want # 1.. And not # 3.  Do I tempt fate and click on # 2 ?)

2 it is..

What now??  It told me that the unsaved changes are still in memory..  Can I turn off the PC now?  Will it blow up??  OK it's safe... It's not a DELL!

😄 😄 😄

Looks like we're on the verge of insanity.. 😉

Should I even be posting this??  They'll send me to an asylum (hope I spelled right).

Here goes...

Submit Post  (after all that's a lot of typing... wonder if anyone actually read it)

😄