LV PDA 8.2 Initialize PDA Button.vi BUG

The Initialize PDA Button.vi for PDA 8.2 is not consistent with prior versions. Here is what the example VI states at C:\Program Files\National Instruments\LabVIEW 8.2\examples\PDA\key events\Key Events Advanced - Pocket PC.vi
Using key events does not override the mapping of application keys. By default, LabVIEW PDA applications do not receive an event when a key that is mapped to an application by the OS is pressed while a LabVIEW PDA application is running. The mapped application launches. You can use the Initialize PDA Button VI to suspend the mapping of application keys while the LabVIEW PDA application is active.
If you load the project and download the exe, in prior version ALL keys that were mapped to applications became disabled. Now only the up, down, left and right keys are disabled. This is a bug. Please fix since it looks like it's just calling the input.dll. Can NI submit to us a new DLL??
Thanks
Robert

Hello,
I have filed a corrective action request (CAR) to R&D for this issue, and have included your sentiments regarding having the problem fixed.
The CAR ID is: 42CA2GSQ
Best Regards,
JLS
Official Note:
This was reported to R&D (42CA2GSQ CAR ID) for further investigation.
Best,
JLS
Sixclear

Similar Messages

How do I Initialize a button to be enabled when the program start and if pressed then disable and gray it until a certain action is taken then comeback to the enabled state?

Hi!!!
I'm doing a program with the following buttons: Run, Abort, Repeat and Exit. When the program starts from the first time only Run and Exit button will be enabled and not disabled so the user doesn't press the Abort and Repeat button. The user has to select from a menu bar the test he wants to make then if he presses the Run button a pop up window will come up asking for the serial number and his name, and will comeback to the main program with the entered information. The user now has to press the Run button again to start the test, when the test starts the Abort button now will be enable
d and not disabled, when the test ends the Repeat button will be enabled and disabled. If the user selects new test from the menu bar the whole process will come again. I'm having problems with the menu bar because it has a time-out and when that occurs the program gets crazy. Also I'm not sure about what mechanical action I have to use for the Run. Do I need to count the times the Run button is press so the 2nd time is pressed it will be disabled. Do I need to use a sequential and where I initialize the buttons so the first time they are like I want (Inside or OUtside the while loop that ends with the Exit button) Any help wil be appreciated.

I'm not sure about the menu bar because i've never used them..i tend to go for listboxes instead.
As for the buttons, if you want to wire the button to a local variable then the button must be a switch, otherwise a latch is ok. But remember you will probably need to reset the button at the end of a run (ie. wire a constant through the while loop to the local variable for the switch). To initialize the buttons at the start, wire constants to their locals outside the main execution while loop.
Put the disabling/enabling functions in the parts of the program the button has activated. For example, you say the 2nd time the Run button is pressed you run the 'test', enable the Abort button and want to disable the Run button - put these property nodes into th
e 'test' sequence/loop.
Sequences are useful to control when you want buttons to be modified. I use them if i cant sequence the order of execution any other way. But try and avoid using multiple frames as it can get confusing if you start hiding code.
If you are still having problems, post an example of your program in no higher than LV 6.0.2 and i will try and adapt it for you.
Kim

How can i initialize a button (Switch when pressed) to be always disabled when i start the programm.

Hello
How can i initialize a button (Switch when pressed) to be always disabled when i start the programm. My problem is that the state of the button is always the state in which it finihed last time.
Thanks
Lukas

A button is either true or false. "Disabled" is a property that determines if the button can be operated or not.
It seems from the rest of your question that you actually want to ensure that it is set to false, but remain enabled. This is easiest done with a local variable as already mentioned by becktho.
If you want to disable the button, use a property node.
LabVIEW Champion . Do more with less code and in less time .

How do I use directional PDA buttons in LabVIEW programs?

Hi all,
I've been assigned to get a LabVIEW program to work on a Palm PDA with LabVIEW 7.0 and palm PDA module 7.0. I am basically totally new to LabVIEW, and my possibly very simple problem is, the PC program requires input from a serially connected number pad for the 8, 4, 5, 6, and 2 keys which are used as four directions (8, 4, 6, and 2) and an enter (5).
I am trying to rewrite the input vi to use the directional buttons and middle enter button on the PDA itself but am having trouble figuring out what to use. I am using a PDA simulator because of the PALM OS5 we own. The input demo vi example provided will not build for PDA because of size so I am unsure of how to approach this. Another thing is, we have LabVIEW and PDA module for pocket PC 8.0, and a Dell Axim PDA on order. From what I understand off of this website, the latest PDA module has example button vi's. I would still like to figure out the way to do this on 7.0 so I can have a better understanding of LabVIEW. Eventually the program's endgoal is to be used on a PDA and inputting with a bluetooth keyboard, but we are going step by step right now.
I guess my biggest questions are, how do I assign the directional buttons on the PDA in my program, and will this differ greatly when we switch to 8.0 and pocketPC.
Oh and I did try to look at the example asteroid.vi but from looking at the input subvi, still couldn't figure out how they assigned the buttons.
Thanks,
Stephen

I can't help with any specifics (no access to the PDA module at the moment and I didn't use the buttons anyway), but I would like to say that it probably would make a big difference if you used LV 8. 7.0 was the first version of the PDA module and was extemely limited and problematic (it didn't even have a tab control). 7.1 was somewhat better and I understand that 8 is even better (although still very limited and buggy).
I also remember reading about several differences between Palm and PocketPC and I think you will generally be better off with the PocketPC as it's related to windows and will probably support more stuff.
Try to take over the world!

LabVIEW PDA button appearance

I have developped an application in LabVIEW 7.0 for Pocket PC.
I need to use version 7.1 to correct some bugs and add functionalities. It seems that the appearance of boolean buttons has changed. I find out how to set background color but I have still a problem with the font. In version 7.0 (Pocket PC 2002) there was a "bold" effect on the button font. This effect is still visible on two button dialog box.
Does anybody knows how to keep this effect (which font to use, what attribute, ...)
Thanks for your help.
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 & 2010 & 2014)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)

Hi,
I don't have a Pocket-PC but a PALM OS based PDA with LV-7.1
The button style of two buttons dialog box is not a bold one. It's a plain font.
I'll ask the question about Pocket PC specifically.
Best regards.
Vincent RUAULT
National Instruments France

Window iphoto to big: no access to upload button and bug

Hi,
I have a problem with my iphoto window upload: she is to big since 2 weeks...I suppose that i'have touched something...I cannot have access to the lower right corner.
For example:if i'm on facebook and want to upload some photos, the iphoto window open and this one is to big .So I cannot access to "upload' button and this window block,bug and i need to quite safari.
If i go to " Presentation" and reduce it,it's not good ( reduce the other window) and if I click on the green button on the left corner its (in my example)for the faceBook page.
Somebody for help me?
Thanks !

Hi...
Login to another user account on your Mac. Try Facebook on Safari there. If it's ok there, then at least you know the issue is just with your user account, not a system wide problem.
If you don't have another user account available, instructions for creating one here.
http://docs.info.apple.com/article.html?path=Mac/10.5/en/8235.html
If you haven't tried turning off Safari Extensions... do that. At least you can rule that out. You can access Safari Extensions from the menu bar, Safari / Preferences / Extensions.

App Store update button displays bug message after updating, iOS 6.0

In iOS 6.0, after updating an app in the App Store, a weird message appears on the update button.
The button remains active giving the choice to update twice or more.

Dude there are many bugs in ios 6 it is not safe to use.

Workaround for keyword button sets bug

Thought I'd post this in case anyone else is beating their head against a wall trying to use custom keyword button sets.
BUG: Control bar sometimes displays the wrong captions for the keyword buttons. Cause: Deselecting a keyword button set in the "Edit buttons" dialog will cause any active button sets after it to appear corrupted in the control bar. For example, with the default set of "Photo Descriptors, People, Stock Categories, Snapshots, ..." try unchecking the Stock Categories button set. When you return to the control bar, use the popup button set selector (just under "Add Keyword") to select Snapshots. Instead of the Snapshot keyword buttons, you will instead see the button captions from Photo Descriptors, though if you click one of those buttons, it will apply the appropriate keyword from the Snapshots set.
Workaround: Rearrange the order of the button sets list in the Edit Buttons dialog to make all checked button sets appear before all unchecked button sets. In other words, don't have any gaps where you have an unchecked button set followed by a checked button set.
Cheers,
Paul

You are my hero!!!! This is exactly what I was looking on here for. Thanks again.

Flash 9 button sound bug? Sound in Over frame plays again when clicked

I've been using Flash for years and I've only just noticed this problem, I guess because I haven't had much call for noisy buttons for a while. In the olden days (FlashMX and earlier) I swear that I could make a button, put a keyframe on the Over frame and attach an Event sound to it, put a keyframe on the Down frame and attach a different Event sound to it and the first sound would ONLY play when the button was rolled over and the second sound would ONLY play when the button was clicked. I just tried doing the same in Flash 9 and when I click on the button, not only does the Down sound play, but the Over sound also plays simultaneously. They're both in the same layer, but the "Over" sound only has its keyframe and the very next keyframe under "Down" is the Down sound.
Switching the sync to Start makes no difference. Synching with Stop on the "Down" frame for the "Over" sound sort of works if there is no Down sound, but there's still a brief snippet of the sound. If I add the Down sound back on new layer, the original problem returns. Of course Streaming doesn't work at all.
This is incredibly maddening, especially since I found this old tutorial on Kirupa that shows exactly what I want, and what I can no longer get in Flash 9, apparently:
http://www.kirupa.com/developer/flash5/buttonsound.htm
I've attached a demo .swf.
Thanks in advance

maijakg,
     You've stumbled onto a good one! If memory serves me right, the Kirupa article indeed shows how this used to work (Kirupa is always top notch), but this behavior changed in one of the recent versions of Flash Flayer. Not sure now if it was 8, 9, or what. It should be easy enough to pinpoint with one of the legacy Flash Players at http://www.adobe.com/go/tn_14266.
     This issue is easy enough to address with ActionScript, which may not be what you want to hear. Still, it's an option. I'll go into that in just a minute. If you want to stick with the button timeline ... well, I'm finding that this proves to be a challenge (and it really shouldn't be). I notice, for example, that I can create an empty movie clip symbol, put my Over sound in frame 1 of that symbol (Event sound), and then drag that symbol into the Over frame of the button.
     That does keep the audio from repeating when I actually click the button -- that is, when I enter the Down frame -- so that does work. You can put your Down audio directly into the button's Down frame, but ... using this approach, you'll hear the Over sound when you release the mouse, even if the mouse hasn't left the button. That's because the movie-clip–with-audio in the Over frame is summoned again when the mouse lifts, and that naturally causes the movie clip in that frame to play its audio again.
     Here's how you can do exactly what you want using ActionScript.
// ActionScript 2.0
var overSound:Sound = new Sound();
overSound.attachSound("sndOver");
var downSound:Sound = new Sound();
downSound.attachSound("sndDown");
btn.onRollOver = overHandler;
btn.onPress = pressHandler;
function overHandler():Void {
    overSound.start();
function pressHandler():Void {
    downSound.start();
     Here's what's going on. In the first two lines, I've declared a variable -- arbitrarily named overSound -- and set it to an instance of the Sound class. At this point, the variable overSound contains all the rights and priviledges of a sound object, because that's exactly what it is. If you look in the Sound class entry of the ActionScript 2.0 Language Reference, you'll see that it has an attachSound() method (methods are things an object can do; they're basically verbs). So in the second line, you'll see that I'm attaching an audio file from the library. In ActionScript 2.0, this happens by way of a linkage identifier, which you can get to by right-clicking a sound and selecting Properties. In the dialog box that opens, you'll see an "Export for ActionScript" checkbox. Select that, and you can type in your identifier, which is just a unique label. In this case, I used the same name as the variable (sndDown) -- only, the linkage identifier is referenced with quotes.
     In the second pair of lines, the same thing happens, but with a different sound.
     In the third pair of lines, I'm referencing the button symbol by way of an instance name. To give a button an instance name, select it in the timeline and then look at the Property inspector. You'll see an "instance name" input field. Here, my instance name is btn, but you could choose whatever makes sense for that button's purpose. In these two lines, I'm simply associating the Button.onRollOver event with one custom function (overHandler) and the Button.onPress event with another custom function (pressHandler). Events are something an object can react to, and you'll see events listed in class entries too. Because we're dealing with a button simple, the class in question is the Button class. When a rollover or press occurs ... I want these custom fuctions to be triggered.
     Finally, the last few lines are the definitions for the custom functions. One, overHandler(), invokes the Sound.start() method on the overSound instance of the Sound class. The other, downHandler(), does the same for the downSound instance.
     The mechanics of the AS3 version are slightly different, but the principles are the same. Instead of linkage identifers, AS3 has linkage classes. When you select that "Export for ActionScript" checkbox in an AS3 document, the identifier input field will be disabled. You'll enter an identifier-like value into the Class field, and the Base Class field will be filled in for you automatically with flash.media.Sound (just go with the default). After that, the code goes like this:
// AS3
var overSound:sndOver = new sndOver();
var downSound:Sound = new sndDown();
btn.addEventListener(MouseEvent.MOUSE_OVER, overHandler);
btn.addEventListener(MouseEvent.MOUSE_DOWN, pressHandler);
function overHandler(evt:MouseEvent):void {
    overSound.play();
function pressHandler(evt:MouseEvent):void {
    downSound.play();
     In this case, you don't need the attachSound() method anymore, because you're invoking the constructor function of each library sound itself (these are linkage classes, remember, and classes create objects directly). The events are managed the same in princple. Once again, each mouse event is associated with its corresponding custom function. In AS3, this happens via the addEventListener() method.
     Finally, the custom functions invoke the Sound.play() method on each Sound instance. Remember, these are instances of the Sound class, even though their linkage classes are actually sndOver and sndDown: each of those inherits its functionality from the base class, which is Sound in both cases. Note that in AS3, the method that starts audio is play(), instead of start(). Just minor differences in syntax.
     Granted, that's a lot to do -- in either version of the language -- just to associate a couple sounds with a button, but off the top of my head, it looks like scripting is the way it has to be done. If I'm wrong, I'd love to hear about it. Maybe there's a simpler workaround!
David Stiller
Contributor, How to Cheat in Adobe Flash CS4
http://tinyurl.com/dpsCheatFlashCS4
"Luck is the residue of good design."

Ugh. Finally got bit by the Lock/Unlock button unresponsive bug.

My phone is over 2 years old.
I have taken very good care of it.
The lock/unlock buttong "just stopped working" yesterday.
Does anyone know what my options are?
I do not have Apple Care.
Will Apple repair this for free?
Can I exchange for a refurbished phone?
Will Apple repair this for a charge?
I've done some research on this subject on the web, and IMHO it's not a "defect" but a poor design-flaw.
It also seems to be a very common problem--too common, in fact, which is very disappointing given that there are so few moving parts on the device and the "home" button and "lock" button are fundamental elements of an iPhone's operation.
Sigh.
J.

First off, thank you for your input.
I would consider that they repair it for free for 3 major reasons:
1) It is not user serviceable--any attempt violates warranty.
2) It is not 3rd party serviceable--without violating warranty.
(So for reasons 1 & 2, I am fully dependant on Apple to resolve the problem. Since I cannot fix it myself, if I go to a third party and they screw it up, at the end-of-the-day I truly have no recourse.)
3) Most importantly, It IS a common problem. A quick google search reveals this. It is NOT a defect, but a design flaw. The choice of "bubble" type switch is not robust enough for the application, there are more simple and durable solutions. Just because you "don't know anyone" or "haven't had the problem" doesn't mean it's not common, and also doesn't mean you may not experience it tomorrow.
Also, you do not have the same model phone as me. It is possible the design is different in your model.
As with most electronics, a 1 year warranty is pointless. Most electronics fail within the first few uses or not at all for quite some time. I have worked a few retail jobs selling all kinds of different electronics. Whether it's a Television, Computer, or Microwave, this is the case with most items. The ones that fail after the warranty, but before 5 years, it is often the case of a design flaw that unlucky customers get stuck with - OR - in fairness, the customer broke the item. I did NOT break this phone. It was working perfectly until a few days ago. It "just stopped." It was very-much a shock, because I had not dropped the phone, nor got it wet, nor exposed it to excessive dust or humidity. (Regardless, it is in an Apple "bumper" case)
The "stuff happens" argument is a very poor one to make for many reasons:
2 years is no where near close to an eternity. With fair & reasonable use, this integral part of the function of the device should last more than 2 years... especially given that I "baby" my electronics. (The phone has not gotten wet.) The iPhone has very few moving parts... they should all last.
An iPhone is a product valued @ $750 (for my model, at the time of purchase)
To have the "on/off" switch of a device worth close to a thousand dollars break after 2 years, that's kind-of crappy. The phone is extremely inconvenient to use without it. And, God-forbid I have an issue and need to reset the phone, I'm screwed.
Maybe in your world $750 isn't much money to you and it's easy to accept a failure such as this. To me, it's a lot of money, and it's insulting to spend another $150 on a replacement, which could then also have the same failure, since no one will know the purpose behind the refurb (in most cases, it's a simple return of the item.)
Apple prides themselves on making the 'best products' in any category they participate in. A failure of a component such as the "on/off" switch through standard use is unacceptable, and should be repaired at their expense.

Pesky table/order button HTML bug

I have some products where I'm pasting in an "order button"
form from Yahoo stores. The code looks like this:
<form method="post" action=""><input type="submit"
value="Order"></form>
I've used it in a previous site with no problems. However, in
my current site, when I paste this code into my table
where the order button should appear, it renders (in both IE
and Firefox), with two unwanted characters displaying
right before the order button ( "> ). You can see this on
the site, to the right of the pipe image:
http://www.pulversbriar.com/gallery1.htm
I pasted the same code into a blank html page, and the
problem vanishes:
http://www.pulversbriar.com/test2.htm
So I can only assume it is something about the table, or the
surrounding div/formatting HTML code that is causing the problem.
However, when I create a new table and paste in the same code, the
problem recurs.
I've been onto the phone to Yahoo about this, and they say
it's a DW problem. I can't see the problem myself, but it
has to be something elementary.... right???
Thanks in advance for any help with this pesky one. If
further information would be useful, let me know and I will post.
-steve

I see no button on that page.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"sbell2200" <[email protected]> wrote in
message
news:e98qq4$dps$[email protected]..
>I have some products where I'm pasting in an "order
button" form from Yahoo
> stores. The code looks like this:
>
> <form method="post" action=""><input
> type="submit" value="Order"></form>
>
> I've used it in a previous site with no problems.
However, in my current
> site, when I paste this code into my table
> where the order button should appear, it renders (in
both IE and Firefox),
> with two unwanted characters displaying
> right before the order button ( "> ). You can see
this on the site, to
> the
> right of the pipe image:
>
>
http://www.pulversbriar.com/gallery1.htm
>
> I pasted the same code into a blank html page, and the
problem vanishes:
>
>
http://www.pulversbriar.com/test2.htm
>
> So I can only assume it is something about the table, or
the surrounding
> div/formatting HTML code that is causing the problem.
However, when I
> create
> a new table and paste in the same code, the problem
recurs.
>
> I've been onto the phone to Yahoo about this, and they
say it's a DW
> problem.
> I can't see the problem myself, but it
> has to be something elementary.... right???
>
> Thanks in advance for any help with this pesky one. If
further
> information
> would be useful, let me know and I will post.
>
> -steve
>

Control.Button disable bug

There is a bug when you change disable state for a Button, the Button state change but not his appearance.
To avoid that put focusTraversable=false.
"Waiting ... Soma ZZzzZZzzz" is a lovely song.

There was a thread about a week ago that covered this. Look for "Set arry
of controls to default".
"AndreasC" wrote:
>>Dear list,>>I've got this problem.>I want to set prgramaticly a boolean
control to it's default value (off).>I use the create->invoke node-> methode
reinit to default.>When the program runs in the developer environment, it
works fine. The >control is set to it's default value. When I make an exe-file
with the>application builder it doesn't work. The control isn't reset to
it's default.>I've upgraded to 601, but it doesn't help.>>Any suggestions?>>Andreas>

Question RE: Button Items and Item Buttons - from "Bug Tracker" Demo app

I've retrieved and installed the "Bug Tracker" Demo app from apex.oracle.com and installed it in my space as I've interest in recreating the custom search bars this application contains (I can't use interactive reports because it appears a bug prevents the ability to remove the "hide column" functionality which is a requirement for me).
I'm perplexed with how the developer of this demo app was able to create an item of type "button" (not normally available as an item type when creating items) and how buttons were created with the sequence value of "Item" versus a sequence number.
How do these interact?
I'm a fairly new developer and as these methodologies are not readily apparent with 3.2's "normal" functionality, I'm quite intrigued to understand how this was accomplished.
I've been looking at this demo app for 2 days in hopes of learning this on my own - still at it but not there yet. Any help you kind folks can provide would be certainly appreciated!
Thanks!
Paul

Dan, thanks for the reply!
I actually figured this out shortly after submitting this post (and confirmed by your post). I had never used a button as "Create a button displayed among this region's items" (versus "Create a button in a region position") before. That apparently is the difference.
My inexperience simply did not allow me to recognize the difference in how apex treats how buttons are created given this choice differentiation.
One more notch in the belt!

Pda 8.0 multi dimensional array support?

I've just spent most of this day chasing down a problem with a vi I was attempting to port from a PC environment to a PDA (PocketPC). I think I have found the problem but I would like some confirmation if this is a recognized problem (not supported) by NI or if this is supposed to be supported but does not work on my IPAQ hx2790 (running WM5.0). The problem I have is that the PDA doesn't seem to support multi-dimensional arrays ... NI, or anyone else who might know the answer ... Is this supposed to be support or not? Thanks
Greycat

That's a great one !
I ran in the same bug a few hours ago (LV PDA 8.0 - iPAQ 4700 - WM 2003) . I could not believe it !!!
It is simply not possible to index a 2D array to extract a single row or column. Yet it is possible to get an array element.
I suppose there are other issues that will be exposed soon.
I have no more time to waste on LV PDA. But I suggest a few search directions : I found that on LV embedded, array operators could not be used with disabled index inputs. In the attached example, I tried to find a workaround and I used a for loop to index each element of a column and build a 1D array. It works sometimes : Don't touch element (0,1) otherwise the vi hangs.
That could be fun if this was not the dead-end of a 2 months work, fighting with LV PDA inefficiencies !
May be I'll try LV PDA again when a new release will be available !
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...
Attachments:
LV PDA 2D Array bug.vi ‏15 KB

Regarding button in selection screen

Hi all,
A query...
After clicking the button on the screen, when i press the execute button it should give a display saying the corresponding button i clicked....
But its not working out frnds...
tables sscrfields.
data flag.
parameters test.
selection-screen pushbutton /20(10) but1 user-command cli1.
selection-screen pushbutton /20(10) text-020 user-command cli2.
initialization.
but1 = 'Button 1'.
At selection-screen.
if sscrfields-ucomm = 'cli1'.
flag = '1'.
elseif sscrfields-ucomm = 'cli2'.
flag = '2'.
endif.
start-of-selection.
if flag = '1'.
write :/'Button 1 was clicked'.
elseif flag = '2'.
write :/'Button 2 was clicked'.
endif.
Thanking u all.
regards,
suraj

Hi,
<b>CHECK THIS CODE now it's working</b>
data flag.
selection-screen pushbutton /20(10) but1 user-command CLI1.
selection-screen pushbutton /20(10) but2 user-command CLI2.
initialization.
but1 = 'Button 1'.
but2 = 'Button 2'.
At selection-screen.
<b>if sy-ucomm = 'CLI1'.</b>
flag = '1'.
<b>elseif sy-ucomm = 'CLI2'.</b>
flag = '2'.
endif.
start-of-selection.
if flag = '1'.
write :/'Button 1 was clicked'.
elseif flag = '2'.
write :/'Button 2 was clicked'.
endif.
Regards,
Priyanka.

LV PDA 8.2 Initialize PDA Button.vi BUG

Similar Messages

Maybe you are looking for