LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Availability of 64-bit LabVIEW for Mac?

Solved!
Go to solution

One more note.  I just figured out that this error is claimed to be fixed for 2011, but it isn't.  Here is the proof:

Screen shot 2011-11-17 at 10.26.57 AM.png

0 Kudos
Message 11 of 32
(1,823 Views)

Ben,

 

As a Mac user and a frequent LabVIEW user, I completely agree with you.  NI does not focus its efforts on Mac/Linux development and it can be very frustrating.  However, I also happen to work at a large corporation and our focus here is to make profit.  Why do I bring this up? Only becuase I think NI is going after the profit themselves and until Mac has a larger market share, we will not see much development on this platform.  Here's a chart from August 2011:

 

OS Usage.jpg

 

 

Right or wrong, NI is just chasing the money.  Good luck in Java man.  Hope to see NI get better with the Macs.

 

Barney

CLD

B Sampson
Ceres Bio Fuels
0 Kudos
Message 12 of 32
(1,808 Views)
Solution
Accepted by RipRock99

RipRock,

 

There's a suble difference between what you've got screenshots of and what we fixed in CAR 257244, per the screenshots in your previous report. What we fixed in 2011 was the behavior of the wildcard character in pattern matching. What your sceenshots cover is the behavior when no wildcard is included. The help on the File Dialog Express VI states:

"If you specify characters other than the question mark character (?) or the asterisk character (*), the VI displays only files or directories that contain those characters. You can use the question mark character (?) to match any single character. You can use the asterisk character (*) to match any sequence of one or more characters."

 

As your observations indicate, this is clearly not happening. I've filed CAR 325220 which covers the case where wildcards are not included in the pattern string. Thanks for bringing up this discrepancy, this is a perfect example of why we need continued customer feedback.

 

While the two problems are very similar, they are unique and require different code changes to fix. I'm glad you're keeping an eye on the bugs you submit. For the time being, you should be able to perform the filtering properly using a *.max string.  I hope that helps!

Verne D. // Software R&D // National Instruments
Message 13 of 32
(1,798 Views)

Verne,

 

U da man, how about fixing an almost 10 year old Mac OSX bug

 

Please noet that there is no way to prevent the user from selecting the max(green) button.

Goto "customize window", it has never been there. Even on of your engineers responded,

can't do it, live with it.

 

Oh just in passing why are mpegs againt de law on a Mac.

 

 

0 Kudos
Message 14 of 32
(1,781 Views)

What da zip. The image pasted into your forum response page but on checking

the post Zippo.

Here is the image

 

But here is an attachement

0 Kudos
Message 15 of 32
(1,775 Views)

However you inserted  your image, you didn't do it right.  The image points to webkit fake URL.

 

You should be using the insert image button at the top of the editor (the image of tree).

 

 

0 Kudos
Message 16 of 32
(1,774 Views)

how old school !

0 Kudos
Message 17 of 32
(1,771 Views)

@Ben_01880 wrote:

how old school !



???

 

What do you consider "new school"?

0 Kudos
Message 18 of 32
(1,770 Views)

Cut and paste

or

Drag and drop.

 

0 Kudos
Message 19 of 32
(1,768 Views)

And where do you expect the actual image file to be hosted so that we can see it?

0 Kudos
Message 20 of 32
(1,765 Views)