Axiom - Input

[andris]

Hi there,

Is there anybody working on the input reader in Axiom?
I modified the Win32InputReader, but am not sure with the DirectX stuff
as didn't work with DX before.

Could anyone take look at that code so we could discuss a bit and offer
a better input reader solution for Axiom? That shouldn't be much work.

Overview of changes I have made so far which are not in SVN:

1. Workaround for the bug making Axiom fail, when input devices are
being lost (when window becomes inactive). Simplified Capture().

2. Joined buffered and unbuffered input. I don't see a reason why those
should be separated, it also conflicted with my simple gui
implementation.

3. Started buffered mouse implementation, is not complete but have
suggestions about it which I'd better discuss.

The current SVN-version functionality is no way broken. What we could
achieve now is:
a) finish buffered mouse input
b) provide an more convenient input interface (already done, could be
said).

(currently no gamepad though)

What do you say?
If anybody is interested I'll send you the current code with more
detailed info about what has been changed and where are the doubts
(seriously only please ;) coz I'm a bit busy with other things, too :(
).

Regards

[Terry L. Triplett]

andris wrote:
> Hi there,
>
> Is there anybody working on the input reader in Axiom?
>

Nope. http://realmforgewiki.castlegobs.nl/index.php/Axiom_Roadmap.
Search for 'input'.
(Note this link is probably days away from being obsolete, but I want to
keep traffic away from the SourceForge wiki until we're ready).

Why don't you repost this to the shiny new axiom developer's list? You
can have the honor of starting the very first discussion.

Mailing list page:
http://lists.sourceforge.net/lists/listinfo/axiomengine-developers

[JW Sullivan]

I know that the input system could use a lot of improvement.  The current implementation is based off of the Ogre implementation, which Sinbad has said was only really added to Ogre in order to be able to have a unified system for creating demo's.  He has admitted that the system could use a lot of improvements, and I know that the system as it stands in Axiom could use even more, since it isn't even feature complete with the Ogre implementation.

 

If you would like to make improvements to the system, you could take a look at the OIS project (Object-Oriented Input System) for some ideas.  It is being created by pjcast (IIRC) on the Ogre forums, and I believe that the source is hosted by SourceForge.  I've used that system a bit, and it has a fairly easy to use interface.

 

I'd say that any improvements to the input system that currently exists in Axiom would be very welcome.

 

J.W.

[andris]

> Why don't you repost this to the shiny new axiom developer's list? You
> can have the honor of starting the very first discussion.
>
> Mailing list page:
> http://lists.sourceforge.net/lists/listinfo/axiomengine-developers

all right, why not? So I'll continue with all the responses there. Just
hope someone reads that, you know brand new list...uhmm ;)

[Terry L. Triplett]

Human nature seems to favor inertia and waiting for someone to make the first move.  Once the first move is made, people usually follow like good little lemmings.  Let's see what happens.  Membership went up by 3 since I posted the above, for a current total of 7.  You won't be alone. 

Hmm.  I don't recognize several of the users.  Hello, lurkers!  Come out of hiding and join in!  You know you want to.  :-)

[Terry L. Triplett]

Quick update after an offline consultation with Borrillis:  To start off with we're going to make the devel list invite only (the archives will still be public) and encourage folks not directly involved in development to frequent the forums and users list.  Nothing nefarious here - just an attempt to cut down on chatter like "'How do I create a material script.?'" and keep discussions focused.  Sorry for the backpedaling - still getting things established, seat-of-the-pants style.

Note:  this isn't necessarily permanent.  The mono lists are open, for example, and work pretty well - breaches of list etiquette are swiftly and sometimes brutally corrected, though they don't happen much.  I lean toward the "open, but you had *better* behave" approach.  But it's harder to put the genie back in the bottle once he's out, so agree with the current approach to start with (I'm the one that raised the question).  Once the project gets rolling again, this can be revisited.

[Terry L. Triplett]

A couple of quick follow-ups:

1) Mailing lists on sourceforge seem to be having a problem. I
submitted a service request, and noticed that many other projects have
reported similar problems - this seems to be a general outage. Please
be patient if you're trying to sign up.

2) To offset the change in access policy of the developer list, I've
created an open users list for the community. If you're not an active
Axiom developer, this is the list you want to join. But note item 1
above and be patient. I'll post back here one more time when the lists
are operational again, if you want to wait.

[Terry L. Triplett]

Ok, SF seems to be somewhat functional again. It's safe to go back in
the water.

URL for users list:
http://lists.sourceforge.net/lists/listinfo/axiomengine-users