08-20-2013 09:25 AM
The LabWindows™/CVI™ 2013 Known Issues list claims that bug ID 357213 has been resolved in CVI2013.
This seems not always to be the case...
Assume an unsaved file in the IDE. Then there are two disk symbols, one in the toolbar, one in the status bar. If I click on the disk symbol in the toolbar, the toolbar symbol disappears (it only shows if the file is modified), but the disk symbol in the toolbar does not get dimmed. It works correct if I use the File / Save menu command or if I click on the toolbar symbol...
By the way, what is the date format in the known issues list, e.g. what does 'Added: 00/41107/' mean?
(for CVI2010 the list looks OK)
Solved! Go to Solution.
08-20-2013 02:43 PM
Sorry for the confusion, here is the corrected description (corrections in bold italics):
Assume an unsaved file in the IDE. Then there are two disk symbols, one in the toolbar, one in the status bar. If I click on the disk symbol in the status bar, the status bar symbol disappears (it only shows if the file is modified), but the disk symbol in the toolbar does not get dimmed. It works correct if I use the File / Save menu command or if I click on the toolbar symbol...
08-22-2013 07:14 AM
You're right, it looks like this issue wasn't completely fixed. I've reopened it.
04-01-2014 03:33 AM
@Wolfgang wrote:
The LabWindows™/CVI™ 2013 Known Issues list claims that bug ID 357213 has been resolved in CVI2013.
This seems not always to be the case...
Assume an unsaved file in the IDE. Then there are two disk symbols, one in the toolbar, one in the status bar. If I click on the disk symbol in the toolbar, the toolbar symbol disappears (it only shows if the file is modified), but the disk symbol in the toolbar does not get dimmed. It works correct if I use the File / Save menu command or if I click on the toolbar symbol...
The updated list of known issues lists ID 357212 as resolved, although it is not, it should have been re-opened... the bug still exists in CVI2013 SP1
04-01-2014 11:07 AM
You're right, Wolfgang. The bug is definitely still open, but there was a mistake in the process of generating the Known Issues list -- it was thrown off by the fact that this bug had been fixed and then reopened. Sorry about that. This will be corrected in the next update.
Luis
08-09-2015 12:06 AM
Resolved in CVI2015