Doors CS [Cur: 5.8 Beta]

DJ_O · Post by **DJ_O** » Wed 25 Jan, 2006 2:30 am

same here

when does your hsoting plan expires?

necro · Post by **necro** » Wed 25 Jan, 2006 1:36 pm

just registered...asked if the gui had options to run off an interupt so you can check for input and then run code "while" the mouse is used. Useful for RTS and shooting games (like duck hunt or house of the dead)

KermMartian · Post by **KermMartian** » Wed 25 Jan, 2006 1:51 pm

They've been going slightly faster lately for me, dunno why.

Necro @ Cemetech wrote:while it is checking for input with the mouse, can other things run "in the background"? Or in other words, will it support a interupt based mouse execution so that things like RTS which would need to run troop AI while the user inputs and when he doesnt also?

Kerm Martian @ Cemetech wrote:I hadn't considered that yet, but it could certainly be done. I can just make another GUI Stack entry type that is a pointer to a piece of code, hopefully not to big so it wouldn't bog the mouse down, to do anything that needed doing while the GUI was working.

@Kevin: October. When it does, I'm going to switch to 818hosting.com - unlimited storage & bandwidth all for $6.95 per month. I've gone to some sites hosted on it and they seem quite fast.

DJ_O · Post by **DJ_O** » Wed 25 Jan, 2006 2:20 pm

aww I though it was something like march ,, oh well

still cool tho

Timendus · Post by **Timendus** » Wed 25 Jan, 2006 3:02 pm

Kerm Martian @ Cemetech wrote:I hadn't considered that yet, but it could certainly be done. I can just make another GUI Stack entry type that is a pointer to a piece of code, hopefully not to big so it wouldn't bog the mouse down, to do anything that needed doing while the GUI was working.

Ehm.. shouldn't that be the other way around?

You should call an interrupt that handles the mouse, main execution should stay with the program. This because main execution = 95% of CPU time, interrupt = 5%. You're not going to tell me that you need 95% of CPU time just to draw a mouse cursor (and are still afraid it gets bogged down), are you..?

KermMartian · Post by **KermMartian** » Wed 25 Jan, 2006 10:48 pm

I was proposing having it not be an interrupt. And yes, of course the mouse uses much much less time. It simply checks direct input for any keys, and returns to the repetitive routine again. But it won't be an interrupt probably; a combo CALCnet2 (if it happens) and interrupt tasker if I make one will be using the interrupts.

necro · Post by **necro** » Wed 25 Jan, 2006 11:52 pm

what does that mean exactly?

Timendus · Post by **Timendus** » Thu 26 Jan, 2006 12:20 am

It means that he's planning to use the interrupts to check for a data transfer from the "network", and he wants to attempt to write some form of task scedular.

I don't see it happening, as usual, but I'm curious to see how far he'll get untill he realises that neither are neccessary, and puts the mouse thingy in an interrupt

KermMartian · Post by **KermMartian** » Thu 26 Jan, 2006 12:29 am

lol...you just can't wait for me to screw up, can you?

necro · Post by **necro** » Thu 26 Jan, 2006 12:36 am

I think I agree with timendus on this...interupts>something probably slower and more confusing

KermMartian · Post by **KermMartian** » Thu 26 Jan, 2006 12:51 am

But it's not gonna be slower, in fact, and it's going to be easier for everyone to code because you won't have to worry about interfacing with an interrupt at all for normal use. For networking, I'm going to make the interrupt reading from and write to buffers.

Timendus · Post by **Timendus** » Thu 26 Jan, 2006 1:27 am

Where are you going to put all that? You have built in routines, that need space + a pointer table, you want an interrupt + it's required jump table, you want data buffers for networking... Is there any saferam left for developers..?

KermMartian wrote:lol...you just can't wait for me to screw up, can you?

Well, I've been waiting for five years

Nah, just kidding. I just think that you're almost always planning things beyond what's realisticly possible, what's useful, and what you are capable of coding.

Andy_J · Post by **Andy_J** » Thu 26 Jan, 2006 2:35 am

Timendus wrote:you want an interrupt + it's required jump table,

Wasn't it figured out that you really only need a handful of bytes for the jump table for an interrupt? I cannot seem to find any verifcation on the Detached Solutions forum at the moment, though...

CoBB · Post by **CoBB** » Thu 26 Jan, 2006 6:28 am

No. Experiments have showed that any of the 256 values can appear in the lower byte, so you do need to use up 257 bytes.

Post by **tr1p1ea** » Thu 26 Jan, 2006 1:13 pm

I do remember there being some excitment because someone thought that the lower byte wasnt as random. But further testing proved that no to be the case. I think Sigma was doing some tests and it sparked a big discussion on the old boards.

You could use an interrupt to run your mouse and perhaps some other small stuff (timers, battery checks every now and then etc) ... but i dont know if it is absolutely necessary.

Either way plans are only plans, im sure lots of things will change as they tend to do once you begin the actually implementation.