Re: [cc65] VICE file formats

> Background: In order not to hog the CPU, the remote monitor code tries
> to give back the CPU to the UI by calling a function to do so (to pump
> the message queue).

So the remote monitor code is not in a worker thread or another UI
thread.  I haven't had a chance to look at the VICE code
yet...unfortunately work life has intervened.

> Unfortunately, this function blocks until there is a message in the
> message queue. Now, if there is anything in the queue, the remote
> monitor code works as expected.

That is the behavior I'm experiencing.  I deduced there's probably no
separate thread for the remote monitor based on my observations.  You
have confirmed that.

> Of course, one could argue that this is bad design in the first place -
> and this is correct. However, it's the way the VICE code works ATM.

I'm not going to start a blame war.  =]  I've been working the UI
elements in NESICIDE to support the plan I emailed out earlier, so
I've got plenty to do.  Good news is I'm already at the point where
I'm trying to interact with the remote monitor...so most of the work
is already done!

Christopher
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.