[wingide-users] debug cursor disappears when using interactive shell

Hi Stephan,
I have been testing what happens on my windowsbox. It is not that different
from what happens on Linux.

When I debug something with Zope and I change a file that is loaded into
wing I eventually get an dialog asking me whether I want to save and restart
or not to save.
If I say restart Zope is killed and somehow restarted. However that never
succeeds.
If I do not save I will get the same dialog over and over.

If I do the same changes with an external editor, Wing just asks me whether
I want to reload the code and everything is fine.

Robert
----- Original Message -----
From: "Stephan R.A. Deibel" <sdeibel@archaeopteryx.com>
To: "Robert Rottermann" <robert@rocad.ch>
Cc: <wingide-users@wingide.com>
Sent: Tuesday, November 13, 2001 5:01 PM
Subject: Re: [wingide-users] debug cursor disappears when using interactive
shell


> On Tue, 13 Nov 2001, Robert Rottermann wrote:
> > I am using wing in conjunction with Zope.
> > When I change any code in Wing a dialog pops up giving me a selection
what
> > to do with the altered file. What ever I answer I have to restart Zope.
> > When I change the code is changed externally of Wing a dialog pops up
asking
> > me whether I want to reload the file. Doing so lets me go on smoothly
with
> > the altered code running.
>
> Hi,
>
> I'm interested to learn more about this.  If anyone else has seen problems
> like this, please let us know at bugs@wingide.com.
>
> Are you saying that if you edit a file in Wing and save, then Wing itself
> will ask to reload the file? Also, are you saying you are using Zope with
> the Reload Product enabled and it fails to reload changed code edited in
> Wing and not code changed with another editor?
>
> Those would be serious bugs that we'ld want to solve.  Also, does it
> perhaps have something to do with your source code being on a network
> server rather than local disk?
>
> We've had some reports of this kind of thing before but so far haven't
> been able to replicate or find any bugs that might cause this.
>
> Thanks,
>
> - Stephan
>
>