Hi,
On Sunday 07 January 2007 21:33, Josh Babcock wrote:
> Yeah, I thought about that, but it would mean a bunch of extra polys.
> Also, if the object in question (behind the switch) is curved, there
> will be a visible seam ... Maybe transparent quads are the answer? I
> would end up looking just
On Sunday 07 January 2007 15:51, Josh Babcock wrote:
> First, this animation is a really good idea.
>
> I for see a problem though. With the old hotspot code, if you wanted to
> animate a really small switch, you could make the hotspot a lot bigger,
> and it would still be easy to hit while you are
Hi,
On Sunday 07 January 2007 22:00, syd wrote:
> My previous problems turned out to be my own errors.
> It sure is nice to be able to add a clickable spot in minutes rather
> than days :)
> Keep up the great work Mathias ...
> I dont know if I like the idea of popup tips for hotspots , sounds
>
Ampere K. Hardraade wrote:
> Err... I think that's a bad idea. One simple reason is that if the user is
> looking at an engineering panel, for example, he/she would never be able to
> pan view. :P
Dynamic view is the headshake system, it has nothing to do with view
panning.
Josh
On Wed, 2007-01-10 at 18:48 -0500, Ampere K. Hardraade wrote:
> How about having the user holding a keyboard key, say Ctrl, which then
> disable
> the dynamic view and enable all the mouse buttons to be used for clicking 3D
> objects? This way, the conflict between panning and object-selection
On Wednesday 10 January 2007 09:04, Josh Babcock wrote:
> It might also be a good idea to suspend dynamic view when the cursor is
> over a pickable object.
>
> Josh
Err... I think that's a bad idea. One simple reason is that if the user is
looking at an engineering panel, for example, he/she woul
On Wednesday 10 January 2007 14:04, Josh Babcock wrote:
> I suggest that we not hold back due to the trim problem until it
> actually happens. I have found that the problems that we predict and the
> ones we actually encounter are often very different. It may not become a
> problem at all.
Indeed,
Ron Jensen wrote:
>
> I am in error. I made a bad assumtion. After reviewing mice.xml I
> realized the pick animation over-rides the mice.xml definitions, so if
> you are pointing to an object with an action defined for button 2 you
> can't switch mouse modes... could be deadly to mouse fliers
On Tue, 2007-01-09 at 16:26 -0500, Josh Babcock wrote:
> Ron Jensen wrote:
>
> > button 0 = Left button
> > button 1 = Middle button
> > button 2 = Right button
> > button 3 = Mouse wheel forward
> > button 4 = Mouse wheel back
>
> Really, we can't use button #2? That's odd, since you *can* defin
Martin Spott wrote:
> Ron Jensen wrote:
>> On Sun, 2007-01-07 at 09:46 -0500, Josh Babcock wrote:
>
>>> If AC authors can't come up with a convention, we will be spending a lot
>>> of time on the users list explaining how to use switches to new users.
>> button 0 = Left button
>> button 1 = Middle
Ron Jensen wrote:
> button 0 = Left button
> button 1 = Middle button
> button 2 = Right button? (can't use this, FGFS internal)
> button 3 = Mouse wheel forward
> button 4 = Mouse wheel back
Really, we can't use button #2? That's odd, since you *can* define it in
mice.xml. Why is this so? Maybe
Ron Jensen wrote:
> On Sun, 2007-01-07 at 09:46 -0500, Josh Babcock wrote:
> > If AC authors can't come up with a convention, we will be spending a lot
> > of time on the users list explaining how to use switches to new users.
>
> button 0 = Left button
> button 1 = Middle button
> button 2 = Rig
On Sun, 2007-01-07 at 09:46 -0500, Josh Babcock wrote:
> Good idea. Also, perhaps we should agree on a convention for how this
> will be used before we end up with a bunch of different methods.
>
> For instance, should a single left click toggle a switch, or should a
> right click always turn it o
Hi all , this works great!
My previous problems turned out to be my own errors.
It sure is nice to be able to add a clickable spot in minutes rather
than days :)
Keep up the great work Mathias ...
I dont know if I like the idea of popup tips for hotspots , sounds
too "gamey" to me , but an interest
Ron Jensen wrote:
> One solution is to make the area around the spot a separate model and
> make that clickable, too.
Yeah, I thought about that, but it would mean a bunch of extra polys.
Also, if the object in question (behind the switch) is curved, there
will be a visible seam ... Maybe transpa
On Sun, 2007-01-07 at 09:51 -0500, Josh Babcock wrote:
> First, this animation is a really good idea.
I've spent the better part of the weekend adding instruments to my F4E,
this code ROCKS!
> I for see a problem though. With the old hotspot code, if you wanted to
> animate a really small switch,
syd wrote:
> Hi all,
> One thing Im unclear on ,reading the documentation , is if the pick
> animation only works with left clicks. Good enough for toggling
> properties , but would still need 2 clickable objects for
> increase /decrease properties .So can a mouse button be chosen with
> this anima
Torsten Dreyer wrote:
> Just a little OT:
> I whould like to see the mouse pointer change it's shape over hotspots or
> pickable objects to show the user the ability to pick something here. Also a
> little popup bubblehelp may be nice. Is it much work to implement something
> like this? Or is it
Just a little OT:
I whould like to see the mouse pointer change it's shape over hotspots or
pickable objects to show the user the ability to pick something here. Also a
little popup bubblehelp may be nice. Is it much work to implement something
like this? Or is it probably already in and I am to
Hi,
On Friday 05 January 2007 21:12, syd wrote:
> One thing Im unclear on ,reading the documentation , is if the pick
> animation only works with left clicks. Good enough for toggling
> properties , but would still need 2 clickable objects for
> increase /decrease properties .So can a mouse butto
On Sat, 2007-01-06 at 19:40 -0800, syd wrote:
> Hi again ,
> Im adding the pick animation to the A6M2 , SO much easier !
> I can only get the >property-assign< to work , but not
> >property-adjust<
> or nasal scripts ... I want to increment / decrement a property. Is
> this being worked on / not
Hi again ,
Im adding the pick animation to the A6M2 , SO much easier !
I can only get the >property-assign< to work , but not
>property-adjust<
or nasal scripts ... I want to increment / decrement a property. Is
this being worked on / not implemented yet
Or am I rushing things or doing it al
Hi all,
One thing Im unclear on ,reading the documentation , is if the pick
animation only works with left clicks. Good enough for toggling
properties , but would still need 2 clickable objects for
increase /decrease properties .So can a mouse button be chosen with
this animation ?
Cheers,
Syd
---
23 matches
Mail list logo
