LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

move window by class name

Does anyone know how to find window name and/or move window using the class
name as input? thanks.

pat
0 Kudos
Message 1 of 13
(5,281 Views)
I think all that stuff is included in lvwutil32plus
utilities found in gtoolbox.topcool.net.
Hope this helps

Gorka


* Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping. Smart is Beautiful
0 Kudos
Message 2 of 13
(5,280 Views)
You can do that.

Infact you have to use some functions of the user32.dll in C:\windows\system32
you can see the vi for more example, but the commands names are in french.

It work with Labview but if you want to create an application that doesn't work good.
If you know more about it...

0 Kudos
Message 3 of 13
(5,159 Views)

Nice reply !

Just 6 years too late... 😄

Chilly Charly    (aka CC)
0 Kudos
Message 4 of 13
(5,155 Views)
that can be useful for others users that have this problem!Smiley Tongue

0 Kudos
Message 5 of 13
(5,142 Views)

"Guig" <x@no.email> wrote in message news:1147329611172-363533@exchange.ni.com...
that can be useful for others users that have this problem! Smiley Tongue


I didn't look into the vi, but when you build an executable, the windows aren't LVDChild class anymore!


That's why it doesn't work with executables. (You can resize a LV development environment window from an executable, though.)


I think they are of the class "executablename" but I'm not 100% sure.


Regards,


Wiebe.
0 Kudos
Message 6 of 13
(5,123 Views)

In fact, I have found how to do:

The executable work well if you delete the copied dll (user32.dll) from the data directory created by application installer.
And maybe that only Labview in french use the window class LVChild... but i don't think so!
And don't confuse window class and window name...
To know the class name, you can use spy++, a tool of Visual studio that gives all informations about windows.


0 Kudos
Message 7 of 13
(5,119 Views)
The user32.dll should be included when you build an application. It's a platform dll, so the user32.dll provided by MS should always used. The dll can differ from system to system.


As far as I know, an exe will use other class names, and since the thread is called "move window by class name"....


If you seach by window name, it shouldn't matter if you use LV or exe, but LabVIEW puts things in the title (like * if the vi is modified, or revision number).


Anyway, if you want to move a vi window (in exe or in LV), you should use property nodes. Guess I dropped into this thread too quickly. I can't see the original question in outlook...


Regards,


Wiebe.


"Guig" <x@no.email> wrote in message news:1147700411720-365122@exchange.ni.com...
In fact, I have found how to do:


The executable work well if you delete the copied dll (user32.dll) from the data directory created by application installer.
And maybe that only Labview in french use the window class LVChild... but i don't think so!
And don't confuse window class and window name...
To know the class name, you can use spy++, a tool of Visual studio that gives all informations about windows.
0 Kudos
Message 8 of 13
(5,119 Views)
I haven't found these properties...

0 Kudos
Message 9 of 13
(5,117 Views)


@Guig wrote:
I haven't found these properties...



Use a Open VI Reference node, and wire the resulting refnum into a property node. Now you have a pleathoria of properties you can reference and the ones you are interested in here are located under the FrontPanel group.

Rolf Kalbermatter
Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 10 of 13
(5,103 Views)