|
|
|
![]() |
|
|||||||
|
||||||||
| View Poll Results: Do you hate or like labview or want to use c?? | |||
| HATE labview |
|
2 | 20.00% |
| LIKE labview |
|
6 | 60.00% |
| Rather use C |
|
1 | 10.00% |
| IDK orbitballs go |
|
1 | 10.00% |
| Voters: 10. You may not vote on this poll | |||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Do you hate or like labview or want to use c
i personally hate it |
|
#2
|
|||||
|
|||||
|
Re: Do you hate or like labview or want to use c
I find LabVIEW powerful, easy to use, and very easy to show others how to use.
On the other hand, I also find running and building code to be terribly, horribly, fingernail-gnawingly slow on the team's several-year-old programming laptop. It's only marginally less slow on the Windows laptop I bought for my own LabVIEW practice last year. I don't regret choosing the LabVIEW path, but I do miss the quick compiling we had with C last year. |
|
#3
|
|||
|
|||
|
Re: Do you hate or like labview or want to use c
LabVIEW RT's build is certainly not as nice as the normal desktop LV experience. No excuses for that. I'm wondering if you are using any analysis VIs, any filters or such. I've been looking into an issue and it involves horribly slow builds on RT when using analysis libs. I think there is a good workaround.
The workaround is to open the build specification for the RT EXE. Go to the Additional Exclusions page and set the checkbox for the libraries so that it only takes the VIs being used. I don't remember the sense of the wording. In my investigation, with this setting, I see normal build times, still a bit slow, but not horrible. I haven't seen any symptoms, but I'll be able to discuss later today why that setting was flipped for FRC. It is the combination of the setting to take all related libraries and the fact that the analysis library is large and interrelated that is causing the big build times. Greg McKaskle |
|
#4
|
|||
|
|||
|
Re: Do you hate or like labview or want to use c
I find i have a love hate relationship with labview. At times i find it nice to see everything clear as day without have to look carefully at sections of written code. On the other hand, its very frustrating when a wire breaks for no reason at all, and then you build long pieces of code only to have a wire break at the end, you delete the code, then realize you actually just messed up on routing a single numeric value (yes, it was a long day for the programmers that day).
![]() |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| I'm trying not to hate labview but... | sparrowkc | NI LabVIEW | 14 | 22-12-2008 22:41 |
| Tip if you ever want to program network applications in LabVIEW | Michael Hill | National Instruments LabVIEW and Data Acquisition | 1 | 24-10-2008 20:31 |
| Which operating system do you use/want to use? | neutrino15 | Programming | 17 | 12-01-2008 00:05 |
| Championship Qualification - Things you like and want to keep | Ken Leung | Championship Event | 4 | 23-10-2003 13:46 |
| which button machine do you use and do you like it? | KenWittlief | General Forum | 10 | 16-10-2003 00:01 |