Michael Aivaliotis

Ok, The merging of posts is normal. It's to prevent multiple consecutive posts by the same author in a short period of time. Actually, it can be used to your advantage if you need to quote multiple posts in the same thread. Just reply to each post and your replies will be concatenated... neat. There is a time limit for merging 60minutes. I'm not changing this.

Now the issue of removing line feeds and spaces, now that's a real issue, it should not happen of course. Any clue to how to make it repeatable? I'll report it when we can narrow it down.

QUOTE(BrokenArrow @ Nov 9 2007, 07:33 AM)

... friend of mine took his laptop and perfectly functioning VI's to France. Upon getting there and doing the last minute changes at the customer site, his EXE didn't work but Dev mode was fine...

Lessons learned. Don't wait until the last second to build the EXE!!!

QUOTE(wevanarsdale @ Nov 9 2007, 12:01 PM)

I agree. A client's desires are not always in full evidence at the start of a project. The key for me is expandability.

I strongly agree with this comment. It really depends on what the code is for. For all customer projects I use a full (event structure inside case inside loop) state machine. The main reason is that ALL code I write changes in such drastic ways due to customer requirements that in the end it makes sense to start on the right foot. Customers come up to me after a project is full under way and ask to add several features. When I respond with: "Sure, just give me an hour and it's done" They are pleasantly surprised. I program with the expectation of that all the time. Expecting otherwise is foolish. Having said all that, there are places where a more simple approach is ok. Only you can be the judge of that.

To comment on User Events. I too am a fond user of them when it comes to interprocess messaging. They have many benefits but I don't think they should be use everywhere (Justin!).

Admin Note: neB Enough with the blank lines already. There are no points for the most use of screen space.

This thread is to announce new pages on the LabVIEW Wiki that have substantial content (ignoring the stubs for now). Chris Relf suggested this and i think it's a good idea. As new pages are added, I will post an announcement here. I suggest others do the same.

Added recently:

Lessons learned from plugins

Keyboard shortcut

Tips and tricks

Glossary of LabVIEW terms

LTR FAQ

List of LabVIEW blogs

List of LabVIEW Champions

Alliance program

Portal:Community ecosystem

NI was able to duplicate the issue with the font size coming across with the text.CAR# = 4F5997F2I'm calling this a "sanity check" bug since this "feature" may be good for the Muge Bearer but under other circustances, this is bad.Ben

The moment we common users can plug into the dev. environment and add our own right-click menus that call our own actions and there is a usable API where we can actually do this stuff then we can talk. Until then, it's all you baby.

QUOTE(Justin Goeres @ Nov 6 2007, 09:59 AM)

...Of course, I'm sure this would probably be wickedly complicated on the back end, to handle all the different datatypes in anything approaching a sane way. But I can dream...

Since when did you start working for NI? Implementation is not our problem.

Another thing. Why, when I have my cursor in a text box can I not use ctrl+A to select all the text? Give me a break.

QUOTE(Justin Goeres @ Nov 2 2007, 08:35 AM)

However (like in the above case, for instance), when someone comes here asking for fundamental definitions of basic instrumentation concepts, they have to be satisfied with a simple link back to another reference site.

That "other reference site" could be the http://wiki.lavag.org' target="_blank">LabVIEW Wiki.

Yet another question about how to call a sub-vi and open the front panel.

QUOTE(mballa @ Oct 31 2007, 07:02 AM)

I like it.

Any Idea how to detect when the "create sub-VI" function has been called?

Well, it doesn't need to detect that but even if I ran the tool right after manually then that would be good too.

QUOTE(Justin Goeres @ Nov 2 2007, 07:39 AM)

:!: WARNING: ZOMBIE TOPIC!!! :!:

Zamboni = Zombie ?

The best advice I can give you is contact a local Alliance Member company in your area for assistance in getting you started with a basic framework which you can take on from there.

QUOTE(Yen @ Nov 1 2007, 09:03 AM)

It seems you've made some changes, but they didn't really help.

Is there any chance of asking the IPB people about this?

Unfortunatly you can only assign one character encoding per forum installation. So I'm afraid it's not possible. The other option is to change the translation to use a non-encoded format. I don't have that translation. In other words, it may be possible with some effort to get a solution but I don't have time.

QUOTE(neB @ Nov 1 2007, 05:57 AM)

Michael,

The last shift up I mentioned above seems to be gone and it SEEMS LAVA is a little faster.

Did you change something?

Ben

Yes, I disabled snapshots preview.

QUOTE(Tomi Maila @ Oct 30 2007, 05:07 PM)

I had performance issues previously a month back but they disappeared when I turned off the snapshots. Maybe you're experiensing the same thing.

Hmm, I think Tomi is right. The snapshot tool slows down the site. Perhaps it's not so great after all.

I haven't been following all the posts so forgive me if this has been mentioned already. One use-case I have is when using the "create sub-VI" function. I don't know about y'all but this feature sucks b***s. Issues:

• LabVIEW gives you a con-pane that matches exactly the number of inputs and outputs you have. For example, if you have 2 inputs and 2 outputs it gives you a con-pane with 4 terminals. I would like to see a standard con-pane and it use only some of the inputs and outputs.
  
• If you have an error in and an error out I would like it to position the error in and error out in the right place AND name the error in to "Error IN" NOT something stupid like error out.
  

So perhaps this cleanup tool in progress can run automatically after a "create sub-VI" action or something? Like a "disconnect all and reconnect correctly" function.

QUOTE(crelf @ Oct 30 2007, 03:21 PM)

Not really a bug per se, but has the LAVA site slowed down dramatically in the last week or so? I thought it was the link at my hotel, but it seems to take ages, irrespetive of my link speed. The banner seems to load okay (takes 4 - 5 seconds), but then the rest takes anywhere between 15 and 45 seconds.

It's fast for me. It might depend on the time of day. No idea. I haven't noticed this. Any others?

I don't have a solution of course.

But you've just proven a point. With VISA you actually have support.

I don't think it matters when the app exits anyway, but it makes the code more readable. Avoids other programmers questioning your intent.

QUOTE(yen @ Oct 10 2007, 10:45 AM)

I remember that one: DetachableStructurePartsEnabled=TRUE.

That is not a real ini key. It's a joke. I have no idea where this ini came from but I am not using this.

Try changing the Color quality of your windows display properties from 32bit to 16bit.

Also, LVOOP is a hog. Are you using LVOOP?

Also, you state that it's an upgrade from 8.2. Have you saved all your VI's??? Silly question but some people don't save (upcovert) all the VI's. A lot of unsaved changes in memory cause this too.

Hmm, high-speed streaming to database. Never been down that path, however I haven't been using the database toolkit either. I just use optimized SQL statements for the task at hand. I call the ADO functions to execute a query. I think there is some overhead in the database toolkit but can't check what the the VI you are calling does at the moment. I thought I had the toolkit installed but it appears to be gone now from my palette.

QUOTE(tcplomp @ Oct 22 2007, 10:17 AM)

Good thing!

Michael could you add this forum to the RSS feed as well?

Ton

I keep forgetting that. It's added.

I just added a new forum, see: Code Repository Code In-Development. This forum can be used by anyone who wants to present some code and evolve a discussion and review where the final product will be a submission to the Code Repository (CR).

There is currently no requirement to start a discussion in this forum in order to have code approved for the CR. Also, just because code is discussed in this forum does not necessarily mean that it will end up in the CR. The current CR requirements have not changed, See: Code repository support forum.

Some other use-cases:

• You can start discussions in this forum and present completed Code Repository code when you need to get feedback from the community (or the CR review committee) before you submit it to the Code Repository.
  
• You have some cool code but don't have time to evolve it into a proper submission. Others in the community can take it over (giving proper credit) and evolve it into a CR submission.
  
• You have an idea and really need some help from the community to get it implemented.
  
• You have finished code and need the community to do some Beta testing before an official CR release. This can also be for existing CR code that has a new upcomming version release.
  
• The list can go on...
  

To get the forum started I moved some existing threads there. I know there are several others I missed. Send me a PM to let me know which others you want moved.

QUOTE(TG @ Oct 20 2007, 04:22 PM)

You are making a good point Nguyen.

I am always amazed at how little I know (the holes in my knowledge) and I been reading LabVIEW user manuals for years.

It would be really nice to see some of the little tricks of the trade explained here. Trust me they are not known by everyone.

Might save someone a lot of grief.

This is why I spent a weekend a while back compiling this http://wiki.lavag.org/tips' and tricks" title='LabVIEW Wiki article on tips and tricks' alt='Wiki article on tips and tricks' style="border-bottom: 1px dotted #3366BB; color: #3366BB; cursor:pointer; text-decoration:none;" class="wiki">tips and tricks page. This is the whole point of the Wiki.

I've added Hebrew to the language list. The next step is to create a dedicated language sub-forum. The biggest step is actually to get the word out to everyone who speaks Hebrew so they can find this forum. That's where the work is. If you feel strongly about it and help then that would be the next step...