WL1

Thanks for your response. It does appear to be a real bug and I have given up on what I originally thought was a simple issue. You have indicated that it still exists in LV9 and I also posted this at ni forums with a response that it is still present in LV10 as well.

Thanks for confirming this for me.

No, the grouping and ungrouping functions are disabled, only the bring forward..move back functions are available. I've tried to make sure that they are all on the same layer with no success. I've also tried to place the buttons inside the control frame, but that didn't work either.

Yes,

That is the only place where you can go to break out the components and customize the control. I went to the tools menu and moved the increment and decrements over to the right side of the control. Once you go back into the edit mode and resize the control, the increment button will move along with the resizing as aspected, but the decrement button stays precisely where it was located in the tools mode (customize mode), regardless of how the control is resized.

Hi,

I need to customize a modern enum in labview 8.6.1. I need to move the increment buttons to the right side of the enum. After moving them to the right side, the decrement button remains in the exact same spot when you resize the enum control, whereas the increment button does what it is supposed to do and moves in conjunction with the control. The problem also exists with the ring control. However, the numerical control functions correctly and both increment and decrement are tied together and move in conjunction with resizing the enum. Grouping is not available when modifying controls. Does anyone have a workaround or fix for this issue?

Thanks,

Wm

Anyone,

I thought I had performed this before, but I'm not finding anything. I am looking for a simple property node, maybe in the VI class or where ever, that will provide me the value that was last pressed on the keyboard. I know that you can get the VKey in the event structure, and that there is a vi to get the keyboard inputs, but isn't there a property node or method that will tell me what the last key pressed was? I'm assuming that if you can get the VKey value in an event structure, then there must be a way to get it through a property or method node as well.

Thanks

I have 8.6.1, installed this "patch" this morning and it killed my LV software. If customer service can't help me out it looks like I have to do a reinstall.

Update: Just got off with NI. Seems this patch is for the base development system only. I have the Pro. My bad.

I still have to remove and reinstall, though.

Paul,

I'm not sure what NI told you, but that does not sound correct!!! I have the full development Suite and I had the problem. And, as I stated earlier, I performed the tasks as mentioned, it took less than 5 minutes to do, and the problem went away. I have not experienced any other problem (related to that) since.

William

Well it isn't obvious to me. Could you post the link?

Thanks,

Ton

Ton

I went to www.ni.com and searched the forums for data entry limits. After reading through similar issues, I found a link to the fix. The link is : http://joule.ni.com/nidu/cds/view/p/lang/en/id/1276, the patch file is: http://ftp.ni.com/support/softlib/labview/labview_development_system/8.6.1/LV861f1DevSystemPatch.exe. It is apparently a problem associated with LV 8.6.1.

I have downloaded the patch and the problem is fixed, roughly 5 min of effort.

Hopefully this solves your problem as well. Let me know if you were able to follow the links I supplied.

William

All,

Sorry if this was obvious to you. I searched NI and found the patch for this bug.

Thanks.

I have created a Type Def Cluster with two Dbl variables, one I32 variable, and one ENUM. LV refuses to update or even change the limit settings that I specify. It is bad enough that LV will not display the correct values when I click on the variable and go to properties...it ALWAYS displays the values that I entered previously.

I want to set the first variable as min: 0.0, max: 1000.0, inc: 0.1

The second variable as min: 0.0, max: 100.0, inc: 0.1

the third as min: 1, max: 1000, inc: 1

LV is refusing to do this. I can not get the variables to respond correctly while setting the type def. and the variables will not update to the correct initial values on my program after I save and apply changes. I have even gone so far as to replace the control in my program with the revised type def and it will not update the values.

Does anybody have any reasoning and solution for this problem?

Thanks

Wm