LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

File dialog trimming the default name

Solved!
Go to solution

Still in 2015!  Hopefully NI can outsmart Microsoft on this one.

0 Kudos
Message 11 of 34
(2,230 Views)

@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.

0 Kudos
Message 12 of 34
(2,218 Views)

Still in LabVIEW 2017 !!!

0 Kudos
Message 13 of 34
(2,132 Views)

@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.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 14 of 34
(2,118 Views)

Actually, it is still present in Windows 10.  It has nothing to do with the LabVIEW version.

0 Kudos
Message 15 of 34
(2,109 Views)

@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.)

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 16 of 34
(2,097 Views)

@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

0 Kudos
Message 17 of 34
(2,082 Views)

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...):

 

file_dialog_bug-1_BD.png

0 Kudos
Message 18 of 34
(2,076 Views)

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":

  • New: when saving over an existing file, it displays a "Do you want to replace it?" dialog.
  • New or existing: Does not display the replace dialog when overwriting an existing file.

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

---
SergioR
0 Kudos
Message 19 of 34
(2,028 Views)

@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?

 

0 Kudos
Message 20 of 34
(1,956 Views)