Hi,
yesterday Jim made the wish to have a beep or seme else audio signal if
Pbuild fails. He is right. But I have another wish: Now not more working
from commandline every second case I encountered Pbuild fail because the EXE
was running from the test before (if I dont expect new bugs from just a
little code change I dont run the exe with debugger but just execute with
Shift-F9) and because of this Pbuild cannt open the EXE. So there should be
either a warning-box appear telling that the exe is just running or Pbuild
shut down the running exe.
What do you think about?

Klemens

Klemens Lichter wrote:

> Hi,
> yesterday Jim made the wish to have a beep or seme else audio signal if
> Pbuild fails. He is right. But I have another wish: Now not more working
> from commandline every second case I encountered Pbuild fail because the EXE
> was running from the test before (if I don´t expect new bugs from just a
> little code change I don´t run the exe with debugger but just execute with
> Shift-F9) and because of this Pbuild cann´t open the EXE. So there should be
> either a warning-box appear telling that the exe is just running or Pbuild
> shut down the running exe.
> What do you think about?

Another good idea.
I think both to have would be nice. A beep for failed Actions like a
pbuild invokation. In case the exe has been executed not within the 
debugger, then VX could check if this process is still active and
warn user about prior starting a pbuild run that is doomed to fail.


Regards
   Andreas Herdt
   [Alaska Research & Development]


> 
> Klemens
> 
>

Andreas Herdt wrote:

> In case the exe has been executed not within the
> debugger, then VX could check if this process is still active

Maybe it would technically be the most simple way to try and open the
target file in exclusive mode... if it fails, it is already running.

And this would work without having invoked the debugging process.

Thomas

Xbase++ FAQ : www.software-braun.de/xbfaq/xbfaq.htm
"Hey, count me *out* of this one! Yeah, sure, taking over the world would
be great, but then what do we do? *I* don't want to have to babysit the
damn thing!"						      -- Dan Sohl

Thomas Braun wrote:

> Andreas Herdt wrote:
> 
>> In case the exe has been executed not within the
>> debugger, then VX could check if this process is still active
> 
> Maybe it would technically be the most simple way to try and open the
> target file in exclusive mode... if it fails, it is already running.

When a process is spawned then you get the process id.
Having this we can easily kill the process on user request
any time.
(Regardless whether it is trapped in an endless loop).

> And this would work without having invoked the debugging process.
> 
> Thomas

Regards


Andreas Herdt


//////////////////////////////////////////////////////////////////
//
// Alaska Research & Development
// Homepage: www.alaska-research.com
// Newsgroup: nntp://news.alaska-Software.net
//
//////////////////////////////////////////////////////////////////

Andreas Herdt wrote:

> When a process is spawned then you get the process id.
> Having this we can easily kill the process on user request
> any time.

You are thinking technically, I'm thinking practically.

There are times when the process isn't spawned from the IDE (but maybe
started from an icon on the desktop), so my solution covers both possible
cases... 

Now you got the idea?

Thomas

Xbase++ FAQ : www.software-braun.de/xbfaq/xbfaq.htm
Remember this, foolish mortals, when ye stare headlong into the
mind-paralyzing void, the inky black nothingness of existence,
the hellish yawning maw of the abyss -- it's pretty damn dark,
so give it a few minutes for your eyes to adjust.
		-- Frank M. Carrano

Thomas Braun wrote:

> Andreas Herdt wrote:
> 
> 
>>When a process is spawned then you get the process id.
>>Having this we can easily kill the process on user request
>>any time.
> 
> 
> You are thinking technically, I'm thinking practically.
> 
> There are times when the process isn't spawned from the IDE (but maybe
> started from an icon on the desktop), so my solution covers both possible
> cases... 
> 
> Now you got the idea?

Sounds weird. Developping an application and starting it from outside of
vx. And then blame vx not be able to handle the situation.

Ok, Ok, you've got the point. VX should check whether the target is
used by anybody. If so, then inform user about and give him the ablility
to shut down the process if VX can do so.

On our todo list is the feature "attach to process". If this one is 
available then user can additionally attach to the process when
trying to debug an application.

Best Regards

   Andreas Herdt
   [Alaska Research & Development]

> Thomas

Andreas Herdt wrote:

> Sounds weird. Developping an application and starting it from outside of
> vx.

Maybe I need to start the application with different working directories. I
could use shortcuts on the desktop for each different data model.

> On our todo list is the feature "attach to process". If this one is
> available then user can additionally attach to the process when
> trying to debug an application.

That would be even better!

Thomas

Xbase++ FAQ : www.software-braun.de/xbfaq/xbfaq.htm
There was a power outage at a department store yesterday.  Twenty people
were trapped on the escalators.		-- Stephen Wright