AnsweredAssumed Answered

vrf-Execute Program(PC)

Question asked by VRFuser on Mar 27, 1998
In message <351AA34C.668E509F@lvld.hp.com>, Greg Goebel
<gvg@lvld.hp.com> writes
>Ger Murray wrote:
>
>>
>> No luck with this for me yet.
>>
>> I tried it and the new iteration of vee with my called program runs
but
>> the caller hangs.
>
>Works fine calling a .VXE program here.  Did you check the Wait for
>Program Exit box to OFF?

You're absolutely right, I didn't click that the caller would default to
waiting until the called was finished.
The thing that made me miss the apparently obvious was the fact that
CTRL-ALT-DEL key combination ( WIN95 ) reported that VEE was 'Not
Responding'. This didn't seem like what should be reported from a
normally running program.

Thanks to all who responded.
>
>Are you trying to *chain* VEE programs or just try to run multiple
>VEE programs?   Loading UserLibraries would be the way to do the
>first thing.
>
>If you want to run multiple VEE programs then the next question is:
>Why?  Something here doesn't quite add up to me.
>
My main need was for a result display program to be started up by the
parent VEE Test Program but be able to run standalone or to useable by
other test programs.
>>
>> My workaround will probably be to make the called program a set of
user
>> functions imported as a library in to the main prog.

This works OK but I feel it's a bit of a kludge.
>> Once I get there, I'm going to decide to use C++.

My main gripe right now is the situation I've had difficulty with before
- servicing key presses on different user interface panels.

Having to have multiple 'Until/Break's pinging each and every button
your user is likely to press so that the button will always be active
seems to me to be really messy.

I'm sure the rules for thread sharing are well established but it's a
real black art getting the execution order to behave in a controlled
manner at times.

The fact that every object needs to have a 'ping' to cause it to be
executed at particular times/events makes programs very labyrinthine.

-----------------------------------------------------------------
What VEE really needs, big time, is a set of system 'ping' sources of
the
type that are typical of other programming languages such as C++,
Labwindows/CVI and Visual Basic such as:

on_mouse_event_left_click
on_mose_position(Width,Height,x,y)
on_key_press(key)
on_hundredth_timer              - Pings 100 times a second.
on_tenth_timer                  - Pings 10 times a second.
on_one_timer                    - Pings every second.
on_srq(address)

And a hundred other system interrupt events that should be accessible to
a hardware interfacing language such as VEE.
-------------------------------------------------------------------
--
Ger Murray
http://www.claycon.demon.co.uk/index.html

Outcomes