locking controls on panel

[PC Programmer]

Is it possible to lock the position of controls on a panel?  How?

[shahina]

Hello,

Unfortunately, is it currently not possible to lock the position of controls to a panel during edit time. However, you are welcome to file a product suggestion for this feature by going to ni.com -> Contact NI and selecting the 'feedback' link.

Best regards,
Shakhina P.
Applications Engineer
National Instruments

[a;lskdjf]

Unfortunately, making suggestions for improvements won't help me any.  I am using an older version and we have no plans to ever upgrade.  In fact, the faster we can phase out of this programming environment, the better.

[Ian.W]

I'm a bit puzzled what the issue is here, but I'll take a guess. 

If you find that your controls on a panel in the UIR seem to shift around or change, it may be that you are editing your UIR file on different resolution screens (e.g. laptop LCD sometimes, and desktop monitor at others), and you have the "Resolution Adjustment" panel attribute set to something other than 0%.

To reset this, double-click on the panel to get the Edit Panel window. Click on "Other Attributes". Uncheck "scale contents on resize" and set the resolution adjustment to 0%. If these are needed when the program runs, they can be set programmatically using SetPanelAttribute when you load the panel, but leaving them this way prevents changes when editing the UIR.

Hope this helps.

--Ian

[a;lskdjf]

It isn't that they shift around from PC to PC.  It is that every time I click on an object to change its  properties there is a tendency to move the mouse slightly.  This upsets the alignment and I have to do it all over again.

I could programmaticaly set the positions whenever it loads a panel, but that is a lot of effort for little gain.  Then, I have another piece of code to maintain.

[Mert_A.]

One way to avoid the double-click drag you describe is to select the "Edit Control" option from the right-click menu of the control -- right-clicking cannot move the control.  Or you can avoid the mouse altogether and use the Tab key to navigate controls and use the Enter key to launch the edit control dialog.  Just don't touch the arrow keys! 🙂

Mert A.
National Instruments

[corvus]

Hello all,

We running into problems after upgrading from CVI 7.1.1 to CVI 8.0 (WinXP SP2, German):

1. Calling GetGraphCursorIndex(...) in previous CVI releases returned negative values (-1) for *plotHandle and *arrayIndex when applied to an empty graph (no plots). Now it will crash reporting a "General Protection Error" (Data Mode: Retain, Copy Original Plot Data: disabled, NULL pointer ???).

2. The distrubution editor reports module dependencie errors for some NI-msm files (nireport.msm,ivipath.msm,...). The reason seams to be a localisation error. CVI looks for these file in "c:\programme\common files\merge modules" but the correct location for a german distrubution is "c:\programme\gemeinsame dateien\merge modules".

3. Building the distrubition kit now takes up to ten times longer then before. By observing the log file (distBuildDbg.log) the processing of  the "component table" and the "property table" consumes most of the time.

Thanks for help

corvus

[Mert_A.]

Hello corvus,

It would be much easier for the right people to see and address your concerns if you start a new thread next time :).  As for the distribution builder issues:

2. You are absolutely correct.  This is a problem we became aware of shortly after release, and the fix will be made available (for free) soon.  It sounds like you have already found the workaround, but if not, all you have to do is create a "Common Files\Merge Modules" directory under "Programme" and copy the NI merge modules from "Gemeinsame Dateien\Merge Modules" to that location.

3. The build can take significantly longer if you are including NI drivers in your distribution (not an option in previous versions of CVI).  Otherwise, the performance between building a new and old distribution containing the same things should not be terribly different.  Granted, there is some overhead involved in moving to the new framework (to allow driver packaging) which cannot be avoided.

I hope that besides these issues, you are having a good experience with CVI 8.0. 🙂

Mert A.
National Instruments

Message Edited by Mert A. on 01-24-2006 10:34 AM

[LuisG]

corvus,

The first problem you brought up, regarding GetGraphCursorIndex, is also a known bug that will also be fixed by the same maintenance release that Mert is referring to. I apologize for the inconvenience. If this is an urgent problem for you and you cannot wait for the maintenance release, if you attach some example code here, I might be able to find you a workaround, depending on how your sequence of function calls prior to the crash.

Luis
NI

[PC Programmer]

Hey, guys!!  You are polluting my thread.  Look at the original subject.