Lovely stuff. For those who were wondering why it seems intermittently
broken, what seems to be happening is the 2D panel hotspots are always
active as well, and they pick up the mouse clicks as well (or instead,
if the 2D hotspot area overlaps a 3D hotspot area). So there are two
places you
Julian Foad wrote:
> For those who were wondering why it seems intermittently broken, what
> seems to be happening is the 2D panel hotspots are always active as
> well, and they pick up the mouse clicks as well (or instead, if the 2D
> hotspot area overlaps a 3D hotspot area).
Are you sure? I tho
Andy Ross writes:
> FWIW, I still haven't been able to duplicate the rogue mouse click
> problem.
Try this:
fgfs --aircraft=c172p-3d
Don't change the view direction or FOV. Click on the ident switch or
the hi/low/off knob on the ADF and watch what happens.
All the best,
David
--
Davi
Andy Ross wrote:
Julian Foad wrote:
> For those who were wondering why it seems intermittently broken, what
> seems to be happening is the 2D panel hotspots are always active as
> well, and they pick up the mouse clicks as well (or instead, if the 2D
> hotspot area overlaps a 3D hotspot area).
Julian Foad wrote:
> Well, I'll put it this way: If I turn the 2D panel on and off with "P"
> while flying "--aircraft=c172-3d", and note where a particular button
> is, and then turn it off so that only the 3D panel is visible, I can
> still click where the 2D button was as well as where the 3D bu
Andy Ross writes:
> Heh, hard to argue with that. Indeed, there was no check for panel
> visibility in the input code. I guess we've never noticed because
> nothing was fighting for the same real estate in the past. This
> one-liner appears to fix the problem.
Committed.
All the best,
How hard would it be to have a property that toggles hotspot visibility? It'd
be nice to be able to turn it on and have yellow rectangles show up on the
hotspots...or something like that. Thinking about making hotspots to control
some of the 3D instrumentation.
Best,
Jim
Andy Ross <[EMAIL PROT
Jim Wilson wrote:
> How hard would it be to have a property that toggles hotspot
> visibility? It'd be nice to be able to turn it on and have yellow
> rectangles show up on the hotspots...or something like that. Thinking
> about making hotspots to control some of the 3D instrumentation.
That's n
I wrote:
> Jim Wilson wrote:
> > How hard would it be to have a property that toggles hotspot
> > visibility? It'd be nice to be able to turn it on and have yellow
> > rectangles show up on the hotspots...
>
> That's not a bad idea.
It's actually an astoundingly good idea, and implementable over
Andy,
> Try the attached patch, which predicates the boxes on the
> /sim/panel-hotspots property. I mapped a toggle event on this to a
> spare joystick button, and had fun. :)
Up until we'll have that pretty menu system soon ;-) would it be hard to
bind a spare key to this by default?
Sincerely
Michael Basler wrote:
> Andy Ross wrote:
> > Try the attached patch, which predicates the boxes on the
> > /sim/panel-hotspots property. I mapped a toggle event on this to a
> > spare joystick button, and had fun. :)
>
> Up until we'll have that pretty menu system soon ;-) would it be hard to
> bi
Andy Ross wrote:
[about making the panel hot spots visible]
Try the attached patch, which predicates the boxes on the
/sim/panel-hotspots property.
That is excellent! So simple, and in conjunction with David's recent
zoom in/out/normal (+/-/=) bindings, it immediately makes clear what's
goin
Andy Ross writes:
> I wrote:
> > Jim Wilson wrote:
> > > How hard would it be to have a property that toggles hotspot
> > > visibility? It'd be nice to be able to turn it on and have yellow
> > > rectangles show up on the hotspots...
> >
> > That's not a bad idea.
>
> It's actuall
13 matches
Mail list logo
