08-10-2016 09:55 AM
Still in 2015! Hopefully NI can outsmart Microsoft on this one.
08-10-2016 12:26 PM
@rob55h wrote:Still in 2015! Hopefully NI can outsmart Microsoft on this one.
Also in 2016.
No, applications that substitute their own file dialogs are worse, much worse!! Using dialogs provided by the OS is the only reasonable option.
12-10-2017 06:41 AM
Still in LabVIEW 2017 !!!
12-10-2017 10:18 AM - edited 12-10-2017 10:19 AM
@jacemdom wrote:
Still in LabVIEW 2017 !!!
I think NI has better ways to spend their development dollars...
...
...
...
...
Like new icons. 😉
As long as I still "do LabVIEW", I will not let NI live that one down.
12-10-2017 11:23 AM
Actually, it is still present in Windows 10. It has nothing to do with the LabVIEW version.
12-10-2017 12:11 PM
@RavensFan wrote:
Actually, it is still present in Windows 10. It has nothing to do with the LabVIEW version.
Well, yes, but... the link you supplied previously in this thread mentioned that a bug report was filed, and that they were looking into how to defeat this bug. (Although I would imagine they aren't looking very hard, and I wouldn't blame them if that was the case.)
12-11-2017 12:02 AM
@RavensFan wrote:
Actually, it is still present in Windows 10. It has nothing to do with the LabVIEW version.
This doesn't change the fact that it still does not work and the users of any commercial apps published in LabVIEW will see it as the app creator's fault, not NI's and not MS's.
I am also pretty sure that NI as circumvented some other shortcomings of Windows in other "more important" issues.
And more importantly this kind of reasoning leads nowhere and solves nothing...if we dig hard enough we will probably find out that it is not even Microsoft's fault...the real fault is on the baby of the freelance software programmer that Microsoft employed for a short while. It was the baby who kept the programmer all night and so the next day he made that mistake!!! 😉
Or was it really the babies fault!? hmmmm...maybe it was the babies mother who had to work all night so that they could pay for the house that they could not afford..lol
12-11-2017 12:39 AM - edited 12-11-2017 12:56 AM
Well, at least not only us, LV programmers suffer from this MS bug 🙂
https://stackoverflow.com/questions/24525606/openfiledialog-cuts-off-pre-populated-file-name
edit: an ugly workaround (if you simulate also a ctrl+a combo, then you get the highlighted state back too...):
07-24-2018 03:40 AM
Hi,
I tried the workaround marked as the solution in this thread. I have LabVIEW 2017 (64-bit) running on Windows 7.
Just to point out a difference in behavior when selecting "New" compared to "New or existing":
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.
Regards,
Sergio
02-26-2019 03:36 AM
@RavensFan wrote:
Actually, it is still present in Windows 10. It has nothing to do with the LabVIEW version.
The bug ist still there for LV 2018. And yes this bug is for LabView version over 2011, couse the same code under LV 2011 and same windows version shows normal behaviour. What makes you think this is a Windows bug?