Microsoft Tablet PC Platform Component, skchui.dll error

[DWeiland]

Hi mrbean,

Probably the easiest way to implent this is to attach a non-latch type boolean control to the stop condition on the bottom loop. Then in the top loop, in addition to writing your Boolean True constant to the stop condition, also write it to a local variable referencing the control in the bottom loop.

The ideal way would most likely be to use queues or notifiers. You can find a good Developer Zone article regarding Master Slave loops here:

http://zone.ni.com/devzone/conceptd.nsf/webmain/5c543b5da8e6925f86256c520052344b

Have a good one!

[mrbean]

How do I create a non-latch type boolean control ?

[mrbean]

How do I create a non-latch type boolean control ?

[DWeiland]

Right click on your front panel and select from the Boolean Palette >> Switch. This is a control which has a Mechanical Action that is not "Latch". This is important because latch type controls do not allow the creation of local variables.

You should probably hide the control as well, since your users won't ever press it. To do this, right click on the control and select Advanced >> Hide Control. If you ever need to find the control again you can double click its representation on the block diagram and it will be highlighted on the front panel.

[mrbean]

I'm sorry for the dense-ness, but I'm using LV8 and in my Buttons & Switches palletes, I see a number of switches but none that are just "Switch" - all of the ones I see have 6 mechanical actions available.

[DWeiland]

I'd recommend either the Slide Switch or Vertical Slide Switch. Or you can use any Boolean you want and change its Mechanical Action to one of the three "Switch" options by right clicking on it and selecting Mechanical Action >> Switch when Pressed.

[RRagan]

I followed Microsoft's workaround and found that it did not work for me.

However, I did find a way to prevent the annoying popup from showing.   Within TestStand click on "Configure->Station Options->Preferences->Debug Options" then uncheck the box labeled "Report Object Leaks" (see attached image).

Message Edited by RRagan on 06-21-2007 11:16 AM

[Sean]

Personally, I would say that completely switching off all warnings may be dangerous.  I have found warnings useful if, for example, I have failed to close any TestStand API references.  If I hadn't been warned then I may have missed it, leading to lots of memory potentially being eaten.