02-26-2019 03:38 AM
For my purpose, I allow overwriting a existing files, but I find it better to display the replace confirmation dialog, so I go for the "New" option, which also solves the filename display trimming issue.
And what do you do, when you need to load a file, and the default filename has to be already filled?
02-26-2019 06:35 AM
National Instruments told me it was a Windows bug. They had reported it, but Microsoft said it was not important enough to fix.
02-26-2019 07:01 AM
@sergey_p wrote:
@RavensFan wrote:
Actually, it is still present in Windows 10. It has nothing to do with the LabVIEW version.
The bug is still there for LV 2018. And yes this bug is for LabVIEW version over 2011, because the same code under LV 2011 and same windows version shows normal behavior. What makes you think this is a Windows bug?
It's a Windows bug because I've seen the same thing happen in other programs that had nothing to do with LabVIEW. Even PC's that had never been anywhere near NI software.
02-26-2019 07:03 AM
@rob55h wrote:
National Instruments told me it was a Windows bug. They had reported it, but Microsoft said it was not important enough to fix.
Yeah, I read this already in other threads. Thanks for the answer.
02-26-2019 07:03 AM
@sergey_p wrote:
For my purpose, I allow overwriting a existing files, but I find it better to display the replace confirmation dialog, so I go for the "New" option, which also solves the filename display trimming issue.And what do you do, when you need to load a file, and the default filename has to be already filled?
The whole filename is there. The bug is that the display of the file name is off the left edge off the filename box. Like Windows had scrolled it to the left even though there was no need to do that since the filename wasn't that long. Hit the home key or cursor to the left and you'll see the rest of the filename appear.
02-26-2019 07:04 AM
It's a Windows bug because I've seen the same thing happen in other programs that had nothing to do with LabVIEW. Even PC's that had never been anywhere near NI software.
I understand, thanks. Never seen this before on windows 7 or windows 10.
Intresting fact: the dialog boxes in any other applications do not set a default file name on calling load file dialog. So this could be a workaround, maybe.
02-26-2019 07:05 AM
The whole filename is there. The bug is that the display of the file name is off the left edge off the filename box. Like Windows had scrolled it to the left even though there was no need to do that since the filename wasn't that long. Hit the home key or cursor to the left and you'll see the rest of the filename appear.
Yeah, I understood this as well. But my users are pretty angry with this kind of stuff.
02-26-2019 07:06 AM - edited 02-26-2019 07:08 AM
@rob55h wrote:
National Instruments told me it was a Windows bug. They had reported it, but Microsoft said it was not important enough to fix.
Microsoft is a company of conceited idiots. Is it a showstopper bug. No. But it is a very annoying bug that affects a lot of people and just looks poorly upon the operating system.
My guess is that the code that handles the file dialog box is so old, no one at MS understands it anymore. And they are scared to look into it.
02-26-2019 07:27 AM
MIcrosoft is a company of conceited idiots. Is it a showstopper bug. No. But it is a very annoying bug that affects a lot of people and just looks poorly.
Absolutely!
I could also reproduce it in C# with the same result.
02-26-2019 08:20 AM
@sergey_p wrote:
For my purpose, I allow overwriting a existing files, but I find it better to display the replace confirmation dialog, so I go for the "New" option, which also solves the filename display trimming issue.And what do you do, when you need to load a file, and the default filename has to be already filled?
Hi Sergey,
I use the filename pre-filled in the case of the user selecting the "Save As" option in my application. For loading a file, I leave the filename empty.