run time focus

[tinnitus]

Hello,

i have  little trouble with a focus on a string command

i set property focus on , it woks perfectly in dev mode but not in runtime

does any one know more about this?

regards

Tinnitus

[chad_vi]

I use the String focus property in several of my programs and doesn't have any

problem in run-time enviroment. It could be settings of your string control. 

Do you wanna post a sample code so we can take a look at it ?

[tinnitus]

hello,

here the  vi  ,

maybe it is not the appropriated property but it act well in dev mode...

Regards

Tinnitus

[SteveChandler]

Try wiring the error out from the value property node to error in of the key focus property node. Or expand the value one to include the key focus property.

Or

[tinnitus]

no it doesn't take effect

i have not indicate that is a called vi , it works if compiled alone but not when called

nevertheless i have no troubles in dev mode even if called

regards

Tinnitus

[SteveChandler]

Interesting. I use LabVIEW 2010 and it works for me.

I saved the project as an earlier version. It has a vi - testpopup.vi that will call your vi when the OK button is pressed. I tested that in dev mode and as a standalone executable and it works.

One note - You might want to consider using error in and out terminals on your vi. I have gotten into the habit of always doing that even when error is wired straight through. I would not need the sequence structure in testpopup.vi.

Open the attached project and run the build specification and see if it works the same when built as it does in the development environment. I suspect that it will.

Are there references to the "filt cmd" in your calling vi?

[viScience]

Maybe in runtime the top level vi window has lost focus.

[tinnitus]

hello

quite special ...

no there is no reference in calling vi

youre vi works but it force me to add a sub fonction ...

i were forced to put the the focus property in the loop, not too effecient but it is ok .....

regards

Tinnitus

[SteveChandler]

Good that you got it working. Having the property node in the loop is definately not ideal but it is just a dialog window so it does not really matter. As long as it works.

But that is never good enough for me. I am always bothered when I do not understand something that I think I should understaned.

In the project that I attached, did the test work both in the development and runtime environments? It did for me. If it didn't work for you in one of the environments then try one of my first suggestions - wire the error terminals from the first to the second property node or expand one to include value and focus properties. Remember that the properties are set from top to bottom. So be sure that set focus is the bottom property.