On Thu, Apr 12, 2007 at 10:29:35PM -0400, Peter Amstutz wrote: > On Thu, Apr 12, 2007 at 09:26:09PM -0400, Reed Hedges wrote: > > > * Change mouse cursor to reflect what clicking will do (i.e. > > differentiate between mouselook/move modes; change when over a hypercard > > or clickable) > > Yea, that would be useful. > > > * If you click some mouse button on an object it becomes selected > > * In the future, could show a panel to edit properties of selected > > object, or create new objects attached to it in scenegraph fashion, or > > whatever > > How do you differentiate between "I'm clicking on this to activate it" > and "I'm clicking on this to edit its properties"?
What do you mean by "activate"? You mean if the objcet has the "clickable" type? Different mouse clicks probably. Or have modes. > > > * If a selected object has the "ui:actions" type that I added recently, > > then display those in a side panel as buttons > > I'll have to take a look at it -- sounds like a generalization of > misc:clickable perhaps? So instead of "I can accept click messages" you > say "I can accept messages X, Y and Z" and specify that "X" is the > default message for clicking. Yes but there's no default currently. A ui:action is like a macro for sending a message to an object that describes the message in a user friendly way. It's implemented in mesh, it prints a list of actions for the current object, and if there's ann action called "foo" you just say "do foo" and it sends whatever message is behind foo to the object. > > > * Some way to show/hide sets of objects in the world, or change their > > properties together as a group (e.g. alhpa to make them fade in and > > out). These groups could be called layers or groups. This would be one > > This sounds kind of complicated, although I agree it could be useful. ... > Let me also point out that you probably shouldn't kill yourself with > crazy new ter'angreal features; the only reason I'm working on it is to I don't think it would be too hard. It's just something I thought of that would be unique and interestincg to show off to people. I was actually thinking of making the layers be metaobjects so others would share your layer selection, useful for collaborative work. Do you think that most of the Terangreal GUI (wx) will be easily transferred to s5, even if the A3DL CS plugin guts are torn out and redone? (Will you post a comprehensive description of A3DL changes in s5 later, like you have been doing for VOS in s5?) When we do demos we actually should have two laptops so people can see what in the scene is shared (and what's not). Reed _______________________________________________ vos-d mailing list [EMAIL PROTECTED] http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
