Joachim

Hi PJM_Labview

Wow, your example is realy fancy, compliment! Very very nice work.

For my luck you have down convertet to LV 8.01.

Thank you for the example.

As soon as I have time, I will try to enhance the picture control.

Is any one intrested in building a little framework?

I think this navigation control would give every application a very professional and userfriendly style.

Greets Joachim

Template at run or edit time? At runtime you can use .vit and at edit time just a simple VI that you save somewhere and copy/rename when you start a new app

Template at edit time. It would be a posible way to copy/rename a VI when I start a new app.

I want to build a complex template, which includes many functions and layout settings.

Thats the reason that I want to outsource the code into a XControl. All the wireing and coding would be hidden, and other programmers will have

a easy template for building apps.

Create the controls is more complex but done once....NET implementation more simple but makes code more complex every time you use it...I guess it depends on your goals...

The suggestion would be to implement the complexity into an XControl. But .NET and XControl is strangely not compatible.

Hi!

Use .NET components from the windows framework.

I built a very simple example, which switches the buttons image all 500ms.

You have to install the .NET Framework 2.0 to use my sample program.

This is much easier than creating for each button with image a new control. Another advantage is, that you can

easily switch the images, create an backgroundimage and so on.

Download File:post-6148-1159112955.zip

If you want to use this in your application, you have to catch the users mouse click with an simple callback VI.

Tell me your experiences!

Greets from Austria

Joachim

Hi!

I also had the picture control in my mind. But the implementation of the control would get out of hand and this means a lot of work and time.

So next week I

It sounds like you want a VI template rather than a XControl. These are easy to create. Simply create a VI that has all the generic functionality you want, then rename or save the file with a .vit extension. It also lets you get around your ".net control inside a xcontrol" issue. I use a VIT to provide myself and my group with a standard place to start off an application. We include our state machine layout and standard set of states, prepopulated with our own particular setup.

I know that professional applications have been built in LabView, mostly because I consider what I create to be professional applications (note: professional does not have to mean perfect). But if you want to move beyond "my" work, you can look at LabView itself, which has several major pieces written in G. You could also check out VIPM which is IMO a professional application written entierly in LabView (8.0.1 if I'm not mistaken).

Hi!

First, thanks for your answers!

Yes i thougt about the option to do this with a VI template. But i want to outsource the code into a xcontrol. If i do that with a VI template, the user of my visualization standard will see the wireing and coding. This could be hidden with an XControl.

I know the VIPM and it

Hi together.

I am currently developing a main application standard for testmachines.

It would be nice to have a XControl with a main menu, logo and some general functions implemented. I have planned

to use this XControl as a standard for each application. So if i want to develop a new test bench, i would drop the XControl into

a blank VI and I will have the main menu (which can be modified by properties) at the right side, the logo at the top and

some properties and methods to save or read parameters from file or network or something like this.

1. Problem:

Implementing .NET Components into XControls.

The .NET Framework has great components, which I want to use for the main menu. I think about the

menu in the Windows Setting Folder. (see atached jpg-file)

Ok, so in a single VI, this all is working fine (VI_works.vi - as an example with a simple progressbar) but if I want to implement the functionality into a XControl I will get an error "Cannot pass a GCHandle across a AppDomain" (VI_doesntworks.vi). Any other .NET Component (also non-Microsoft Components) doesn