Michael Aivaliotis

Well, I played around a bit and I got it working. You can now drop data onto the graph, however the drag enter still does not work. See attached (8.2.1).

QUOTE(jaegen @ Jul 9 2007, 12:02 PM) I don't think this is related. The link you reference affects any control not just graphs. QUOTE(ptit bras @ Jul 4 2007, 07:59 AM) Is it a LabVIEW bug or I forget something ? I think this is a bug. I tried to simplify the example and I removed the drag enter events on the DD_Main.vi. It still locked up. Also, I tried to simplify even more... I removed drag enter event from the Facade and I only used Drag Drop. I could now see the data name (without lockup) but when I probe the get drag drop data function error out, I see error: http://forums.lavag.org/index.php?act=attach&type=post&id=6334''>http://forums.lavag.org/index.php?act=attach&type=post&id=6334'>http://forums.lavag.org/index.php?act=attach&type=post&id=6334 I would report this to NI for sure.

QUOTE(jccorreu @ Jul 9 2007, 04:35 PM) I don't have an explanation for trying to register events on an idle VI, however I think I read somewhere that the VI should be running or reserved for running in order to register for front panel events. Your assumption about "wait until done" is false. It has no affect on your problem. The issue is a http://wiki.lavag.org/Race_condition' target="_blank">race condition. You are performing the two tasks in parallel. It worked when execution highlighting was on because the VI was running before the registration happened. The slowdown gave the VI more time to run. The second approach is better since there is more chance that the VI will be running by the time you do the registration. I have even seen the second approach fail under certain conditions because the VI to run is very large and takes a while to load into memory and execute. By setting "wait until done" to false LabVIEW issues the Run VI command and keeps going on to the next piece of code without checking to see if the VI is actually running. If you really want determinism, there needs to be some kind of handshaking where the caller waits for confirmation that the VI is running before continuing.

QUOTE(Aristos Queue @ Jul 9 2007, 07:26 AM) Just for completeness, I want to remind people that if you use a case structure to comment out code AND you still want it to stay in memory, you now need to use a boolean control on the front panel set to false instead of a boolean constant. The LabVIEW compiler is smarter now and will not include code if it's inside a case structure with a boolean constant set to false.

QUOTE(John Rouse @ Jul 7 2007, 11:10 PM) This is correct. Locking, writing then unlocking in a loop is bad and should be avoided unless the core of the OOP framework is optimized. For example, using the http://wiki.openg.org/OpenG_Class_Templates_for_LabVIEW_Object-Oriented_Programming' target="_blank">OpenG Template for queue based by-reference classes.

This is a known issue. Can't remember how to fix it but I think this is how: Installing LabVIEW 8.2.1 On Top of LabVIEW 8.2 Causes Broken VIs and Libraries I had the same problem and it was driving me nuts.

Clean up all block diagram wires

QUOTE(John Rouse @ Jul 6 2007, 09:23 PM) The main benefit of naming queues is if you are obtaining a queue by name somewhere. If not ,then this has no benefit. Queue references don't need names. QUOTE(John Rouse @ Jul 6 2007, 09:23 PM) The whole idea is to have a memory location that is specific to the process (object) instance and only that instance. This way two or three process's can operate independently and each process can have a method for doing/updating and seperate (reentrant) methods for monitoring. I'm not sure I follow. What OO framework are you using? OpenGoop, LVOOP? If you create a new instance of your object then doesn't each instance already have a place to store data? QUOTE(John Rouse @ Jul 6 2007, 09:23 PM) I understand the notifier but admittedly the behavior of notifiers is something I seldom can think of a "use case" for in my programming. Whats a really good use case for a Notifier (over a queue) anyway? Notifiers are basically occurrences with data. usually used to "wake up" loops and at the same time pass data to them. With the release of dynamic events and event structures, they become less important however still useful sometimes.

QUOTE(ohiofudu @ Jul 6 2007, 08:00 AM) Always. Old photos can be found http://forums.lavag.org/gallery.html' target="_blank">here.

You don't have to re-submit a zip file or even a screen-shot. Just leave those fields blank.

Btw, I really don't like that yellow background on the diagram. It doesn't feel right. Or is it just a side effect of the gif transform?

you can avoid the search if you just want to sort. http://forums.lavag.org/index.php?act=attach&type=post&id=6213

Yes, you could do this. The XControl is always running so I don't see the problem. You could have the event structure register for events of interest.

I don't think you have a choice.

This will be overkill to use a motor controller. If you just want to flip a door open on a doll house, the easiest way is to use a relay. I would rig the door on a spring tension mechanism that is kept closed on a latch. Popping the latch would unlock it and the spring tension mechanism would do all the work of opening the door. You could use cheap digital IO hardware to control the relay. You used to be able to buy $50 DAQ hardware from MCCDAQ but the NI acquisition caused all their prices to go up. So much for competition.

QUOTE(John Rouse @ Jun 22 2007, 09:48 AM) Admin Note: Next time, you don't have to repost. Just click on the report post button at the bottom left of the post. Then type your request into the text box. An admin will move the post into the right forum.

Hey! I just got the results from my CLA re-certification. I passed again!

QUOTE(yen @ Jun 20 2007, 10:49 AM) I'm not sure. I did a search on "kermit mel" and it came right up.

I would add this to the wish list. It would be nice to have a little icon next to the object like a little mini post-it note. Then by clicking this it would popup a little description overlay (no stupid modal dialog).

QUOTE(yen @ Jun 4 2007, 10:42 AM) I've changed another setting on the forums. Can you verify that Get New Post still works as expected?

Just want to say that this issue is now resolved. Outline mode links work again.

Google Public Policy Blog

I felt like singing like that today as I was debugging my lvoop objects... My eyes bulged like that when LabVIEW crashed midway through it.

QUOTE(Ben @ Jun 18 2007, 11:07 AM) Imagine pair programming with your boss. That's rough right? Now add to that the fact that it's Jim Kring... Welcome to my world!

QUOTE(hooovahh @ Jun 18 2007, 01:30 PM) 1974.