12-18-2007 03:32 AM - edited 12-18-2007 03:33 AM

We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
12-18-2007 03:53 AM
The problem is that when the search window first loads, it seems to do a recursive listing of all the palettes and that takes time.
I know that NI has this on its radar, since Darren presented a prototype of a better way at NIWeek, but with NI's timetables, I wouldn't expect to see it implemented for at least a year.
After seeing Darren's prototype, I decided to write my own, and you can see some results in this thread. I am working on this, but I don't have too much time for it, so it's going slow. I do have a much better version than the most recent one on that thread (posted in reply 31), so I'll see if I can clean it up and post it. The main problem with it is the exact thing that works around the problem you described - it doesn't parse the palettes, so all the listing needs to be handled separately.
12-18-2007 04:23 AM
@tst wrote:NI has this on its radar, since Darren presented a prototype of a better way at NIWeek, but with NI's timetables, I wouldn't expect to see it implemented for at least a year.
I was assuming so... but what surprised me is that if you launch the search from a subpalette because you know the function you're looking for is inside of it does load faster, I was hopping it would only load the hierarchy of the subpalette from which you launch search and apparently it does not. I think just this simple restriction would make the search more attractive.
@tst wrote:
The problem is that when the search window first loads, it seems to do a recursive listing of all the palettes and that takes time.
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
12-18-2007 09:44 AM
12-18-2007 10:12 AM
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
12-18-2007 10:21 AM
12-18-2007 10:28 AM
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
12-18-2007 12:39 PM
I don't know about 8.5, but my 7.0 is also configured to load palettes in the background and I still seem to remember that it takes it about 10 to 15 seconds to load when first called, even if I do it after using LabVIEW for a while (I use it rarely, so I can't really remember). I believe the only toolkits I have installed are the RT module, the DB toolkit and the control\PID toolkit. I also have some user.lib VIs, which probably slow this down.
@jarrod S. wrote:
LabVIEW 8.5 addresses this problem by loading the palettes in the background after you first start up LabVIEW.
12-18-2007 12:54 PM