Michael Aivaliotis

It seems like your approach will work. I wrote a different version of your method using only queues and no user events. The wait function in the proxy loop can be removed without problem. I just kept it to be consistent with your implementation.

QUOTE(yen @ May 3 2007, 11:13 AM)

The servers are relatively slow as it is and the interface becomes inconvenient when there is a large number of posts to go through.

The server is the fastest it's ever been. It's a dedicated machine. There is room for upgrade but it's already at about $109US a month which is about breaking even at the moment. Also, we are located in North America so regardless of speed your location will also be a factor. I'm wondering what feature of the NI forums makes it better for viewing a large number of posts? can you elaborate?

You can open multiple copies of MAX. Perhaps this will fulfill your use case.

QUOTE(Noxious @ May 2 2007, 07:36 PM)

I have used LabSQL and actually got it to connect to my DB but I had to use the MySQL ODBC 3.51 Driver. However, I don't think installing this driver on every PC that I deploy my application on is a very practical solution.

Perhaps it's not practical in your situation, but essental. I can't think of any other way to connect to a database without a driver of some sort. The MYSQL driver comes with an installer. Do you have an installer for your LabVIEW application already?

We are NOT going to implement a reputation system. This was an old thread that was dead and now resurected. We will not implement any type of voting system either. Please see here for my response on other issues raised in this thread.

QUOTE(yen @ May 2 2007, 12:41 PM)

I would suggest again the suggestion we made once of having a very simple LabVIEW test in order to register.

This is out of the question. All are welcome here on LAVA. I don't want to exclude anyone. Some may want LAVA to be an exclusive club but quite frankly, if it comes to that, it will cease to be interesting for me. In addition to that, the forums will die because everyone will be a lurker reading Tomi and AQ's posts on Greek philosophy.

This discussion is going in the wrong direction. My original comment was not to HH's or newbies. It was directed towards the forum regulars. Be nice! We all already acknowledge that Homework Huster's are not liked. Fine, that is an issue separate from all other. Other than that, ALL other questions are welcome whether they be simple or complex. I am the first to post stupid questions here on LAVA. If we don't then NI will never fix the problems that plague new users of a feature. Remember, we are all new when it comes to the introduction of new features regardless of how long you use LabVIEW.

There has been discussion of forwarding new users to the NI Forums. Again, the wrong attitude. I mean, if that doesn't sound like "we don't want your kind here" I don't know what does? Forwarding people to the NI Forums is not acceptable. Links to solutions or key examples/articles are fine but a general "brush off" to the dark side is just wrong and insulting.

In order to put a closure to this discussion, I am implementing the following policies/procedures:

1. Homework Hustlers are not allowed on the Forums. No exceptions.
   
2. If you think a certain post is a homework hustling type question. Click on the report post to moderator button. This is the only recourse available to you. DO NOT respond to the post. You are not a moderator and posting negative or disrespectful comments will be considered abuse and results in a penalty by suspension of your account for a period of 2 days. If a post has been determined to be a Homework question, the guilty party will be contacted via PM and a clarification will be requested. If the issue is still not resolved to the satisfaction of a moderator, then the users' account will be deleted and all their posts removed.
   
3. In general. Do not post comments to any discussion about how the user will be better off on another website or forum. Any comments that imply that the original poster is not experienced enough in LabVIEW or should not be on LAVA is considered disrespect and follows the same 2 day suspension penalty.
   
4. Moderators: Only the moderators are authorized by the LAVA Forums to perform any user account suspension/deletion, post editing, post deletion and post moving. In addition, only moderators can decide if a post is a Homework question. Moderators do not read every post. This is impossible. Please use the report post to moderator button to bring anything to the attention of a moderator.
   
5. Posting in the wrong forum. Do not respond to a post located in the wrong forum to let the user know it's in the wrong forum. This is the job of the moderator since they have the power to move the post. Again, please use the report post to moderator button. Making comments of this fact is considered impersonating a moderator and is not acceptable.
   
6. Spam: If you think a specific post is clearly spam use the report post to moderator button. Replying to such posts only adds visibility to them and makes the problem worse.
   
7. Personal Messages: Do not use the personal message (PM) system for LabVIEW technical support, dating, abuse or LabVIEW SN requests. If a member reports to a moderator that their PM inbox has been abused(for any reason) then the abusers' account will be suspended for 4 days.
   
8. Member's privacy regarding moderation decisions. All moderator decisions and outcomes (suspensions, deletions etc) will be kept private and confidential. This will allow offenders to recover from what may possibly be a mistake or error on their part.
   

I will add these rules to the [wiki]Forum Guidelines[/wiki] as soon as I can.

I am aware of this issue but didn't think it was critical enough to fix. Now that it's "noticed" I guess I have to fix it now...

See here:

[wiki]Converting a Sensor Voltage Input to Physical Units[/wiki]

QUOTE(crelf @ May 1 2007, 10:07 AM)

It's even easier: just click on " ! REPORT " next to the post.

Yes, exactly. Members should always use this feature any time they want my attention drawn to a post. I can't be everywhere but the Report Button is the most effective.

This issue is now resolved. Sorry about that.

QUOTE(tcplomp @ May 1 2007, 12:07 PM)

I get this message for all LAVA rss'es from Wizz RSS

An invalid XML was returned from http://forums.lavag.org/index.php?act=rssout&id=3 (LAVA Bug List)

Also id 9 (LAVA LabVIEW 8) and 2 (LAVA All Programming Discussions)

Only - ALL of LAVA - (id 8) works OK

Ton

tcplomp let's not confuse the issue. LAVA Forums only has one RSS feed and it's working fine. The others you cite have been discontinued for months. The only LAVA Forums feed you should be using is => http://forums.lavag.org/index.php?act=rssout&id=8

crelf It appears that an older Blog post of yours is not generating proper XML output thus breaking the feed. I'll look into it more.

I've sent a support request for this issue. It should be resolved soon.

The blog is not offline. It appears to be a RSS format issue since FF loads it fine. I'll look right into it.

It's very simple to enact a policy that bans homework type questions if we all agree. If any slip through, a simple PM to me and their post and account is removed.

Now this is a good candidate for an XControl if I ever saw one.

QUOTE(Val Brown @ Apr 30 2007, 06:34 PM)

Yes, I agree -- and here's where I see the lack of value in using an XControl. Now I'm NOT asking for all of the following functionality to be included in a posted example but I am pointing out that -- at least as far as I'm concerned -- there are shortcomings to using XControls in real world, deployed code. I HOPE the shortcomings that I see relate more to my own lack of familiarity with XControls but....

Now to me it's easier to architect all of that NOT in an XControl but in the "older" architectures of QMH or ESM using typedefs, etc.

What you are describing is a complete application on its own. This can definitely be encapsulated into a single VI. If you need to use this functionality then you can call the VI and embed it into a subpanel. Why not?

QUOTE

I disagree with this. If you ever have to use multiple property nodes to manipulate and customize a UI then this is a good candidate for an XControl. You are not manipulating hardware, you are manipulating UI components based on user interaction or possibly interlock conditions. Based on my experience, manipulating UI's to handle users takes 10 times as long as hardware communication. XControls allow you to reuse this UI code.

Having stated all this, it does not mean you cannot implement hardware interaction or tasks that take a little too long inside of an XControl. You can always launch parallel process VI's for that. This requires a little more effort on the part of the programmer and is not a built-in feature of XControls.

QUOTE(Val Brown @ Apr 30 2007, 05:26 PM)

"CD drive" means CD-ROM so I would like to see an example of an XControl that would involve all of the "transport" controls of a typical CD-ROM control program - something like a media player's Stop, Play, Pause, etc...

I don't mind working on this however, the requirements seem vague. The XControl should not actually implement any of the functionality. XControls are mainly for UI implementations. What does your data type look like? You say you want Stop, Play, Pause but you can just as easily assemble this inside a cluster typedef. One thing I can think of is a Play button that after being pressed, turns into a pause button. I think we should work on the requirements first:

• Must have a Play, Pause, FF, FR button
  
• Play button will turn to pause after it's pressed.
  
• Should have a progress indicator. Progress of what? Music?
  

QUOTE(tcplomp @ Apr 30 2007, 06:17 AM)

Dissapointing but not surprising. XControls are not easy to master. BTW, I'm giving an XControl presentation at NIWeek this year. Those that are afraid of XControls should attend.

Ok, it turns out that this is a preset program without any smarts to identify the proper movements. Just a movement experiment. Works well...

BTW, the woman next to her is her Mother!

QUOTE(xtaldaz @ Apr 30 2007, 10:58 AM)

Ummm, thanks for the ummm...help. There are so many comments I would love to make, but I will refrain.

I think that's best. . Btw, is does your avatar happen to be a jackrabbit?

This is really nice. Not sure if the NXT is looking at the colours or just doing a preset routine. Excellent nonetheless.

Hey, I put a warning up... and I put it in the LAVA Lounge. Besides, I'm just trying to raise awareness. Tryin' to help the ladies out there...

Warning! Beware of Language Content! Use Headphones...

She offends me and turns me on at the same time...

See Here:

http://forums.lavag.org/Wiki-LAVA-Forum-Gu...ines-t7691.html

Let's hash out the LAVA Bible.

QUOTE(Gary Rubin @ Apr 28 2007, 06:26 PM)

Am I advanced enough? Am I really an "architect"? I shouldn't have to think such things.

Everyone is welcome here as far as I'm concerned. People already know that this website is called LAVA and what the two A's stand for. Perhaps they all want to learn from the experts, I know that's what I'm here for. I'm always learning something.

QUOTE(PaulG. @ Apr 28 2007, 08:01 PM)

I agree with you on this. I have always been open about sharing my knowledge about LabVIEW. I have put on countless presentations at various LAVA meetings because I truly believe that we should all be programming at the same advanced level. Those that think LabVIEW is not powerful or cannot do this or that, think that way because no-one has shown them the light. We all need to give up our secrets for the common good.

QUOTE(PaulG. @ Apr 28 2007, 08:01 PM)

LV

Yes, it's about getting at the root of the feature or technology and figuring out "why the hell should I use this, and why should I care". One of the reasons I started the Wiki section of the site is for this reason. There, we have more time and can focus on explaining features and how to use them in various use cases.

Recent posts have been downright mean! If you don't think the topic is worthy of your time or effort to respond then move along. You don't have to respond. Especially not with a smart ass remark that just makes you feel better. Veterans around here lately seem to be ganging up on new members in the same way schoolyard bullies do. Yes people, we know you're ace LabVIEW Guru's and it seems very silly for someone to be asking: "How do I get a VI to pop-up when I click a button". Well, I was in the same position when I started LabVIEW. It took me 3 months of development before I found out how to do this simple thing myself! In the end, my company hired an Alliance Member to come in a show me this and other tricks. I only wish I had something like LAVA back then.

What are you doing to help? Why not write a Wiki article describing how to do this? Why stop there? Write an article on all of the issues plaguing new users. I am appalled at the tone and treatment of new members and those where English is not their first language. It's unfortunate that LabVIEW is not a very popular language since those members cannot find help in their native tongue and so resort to joining English forums for help. It is what it is. If in doubt, ask probing questions, get to the root of the issue. Be constructive and helpful. If not, don't respond! Please.

It used to be that, if you were a LabVIEW user among users, there was a certain bond. Others would help you overcome hurdles and get you hooked on LabVIEW. What ever happened to that?