> Sound like a good idea . I don't get smooth results without some nasal
> help , but its so much nicer to move the mouse in the direction you
> want to push the lever rather than clicking 2 hotspots or two separate
> mouse buttons for forward/back.Having this routine in the global nasal
> should a
Sound like a good idea . I don't get smooth results without some nasal
help , but its so much nicer to move the mouse in the direction you
want to push the lever rather than clicking 2 hotspots or two separate
mouse buttons for forward/back.Having this routine in the global nasal
should also save m
Syd,
I did some experimenting with the new properties. Here are my results that I
have for the SenecaII:
A nasal mouse motion handler:
var MouseHandler = {
new : func() {
var obj = { parents : [ MouseHandler ] };
obj.property = nil;
obj.factor = 1.0;
obj.YListenerId = setlis
Ive tried a few solutions to zero the properties , but then the
animation stops working .With the current implementation , the mouse
can leave the picked object while the button is pressed and continue
to move the lever , so for the moment this
seems to work ...
On Sat, Jan 8, 2011 at 1:27 AM, T
> I knew this was too easy , and looking for the reason , but the
> acceleration properties don't zero out when the mouse stops moving .
> While it still works to a point , still not quite right.
Hmm - I have no idea how to solve that. Our mouse motion handler gets called
with "last movement since
No problem , and thanks . Imagine where flightgear would be now if
everything worked the way it was meant too on the first try :)
On Sat, Jan 8, 2011 at 1:13 AM, Torsten Dreyer wrote:
>> could you invert the y
>> acceleration before updating the property ?
>>
> Sorry, my bad. It's inverted now.
>
After a quick investigation , i see that the acceleration properties
are only updated IF there has been a mouse movement , so they retain
the last value ... my oversight.
Should I make a patch , or leave this to you Torsten ?
Cheers
On Sat, Jan 8, 2011 at 1:03 AM, syd adams wrote:
> I knew this w
> could you invert the y
> acceleration before updating the property ?
>
Sorry, my bad. It's inverted now.
Torsten
--
Gaining the trust of online customers is vital for the success of any company
that requires sensitive
I knew this was too easy , and looking for the reason , but the
acceleration properties don't zero out when the mouse stops moving .
While it still works to a point , still not quite right.
--
Gaining the trust of online c
Brilliant, a huge leap over click-click-click. Thank you Syd!
-Gary aka Buckaroo
On Fri, Jan 7, 2011 at 12:45 PM, syd adams wrote:
> Hi guys.
> Is there any interest in mouse acceleration properties, besides myself ?
> I,ve added it locally , and have mouse drag pedestal controls in the
> Aer
Hi Torsten , i have one little request , could you invert the y
acceleration before updating the property ? I had it inverted
originally , otherwise you get negative values pushing the mouse
forward , positive pulling back. It could be inverted with nasal for
use , but it feels more natural with po
Thanks,now I can undo my nasal versions.I didn't want to get too far
in case the idea didnt fly;)
On Friday, January 7, 2011, Heiko Schulz wrote:
> Hi,
>>
>> Good idea, and cheap to implement. I just pushed the patch
>> with some tiny
>> modifications. I added some code cleanup, too, to make it
Hi,
>
> Good idea, and cheap to implement. I just pushed the patch
> with some tiny
> modifications. I added some code cleanup, too, to make it
> look more worthy
> than a 2-line-patch ;-)
>
> Torsten
And now we need just a good documentation in how to use this feature.
> > Is there any interest in mouse acceleration properties,
> > besides myself ?
>
> Defenitely yes! Much, much nicer/realistic for levers!
>
>
> Gijs
>
Good idea, and cheap to implement. I just pushed the patch with some tiny
modifications. I added some code cleanup, too, to make it look mor
On Jan 7, 2011, at 1:13 PM, syd adams wrote:
> Yes, the two lines of code I added just write the mouse xy movement to
> properties.With nasal I have to calculate the movement,which is done
> in the mouse code already.I've set up the Aerostar so I can click and
> slide the throttle,mixture and pro
> Is there any interest in mouse acceleration properties,
> besides myself ?
Defenitely yes! Much, much nicer/realistic for levers!
Gijs --
Gaining the trust of online customers is v
Yes, the two lines of code I added just write the mouse xy movement to
properties.With nasal I have to calculate the movement,which is done
in the mouse code already.I've set up the Aerostar so I can click and
slide the throttle,mixture and propeller levers in pairs, or
Shift-drag to move each leve
Hi,
Can you explain it a bit more detailed?
Is this the same as the manual which you move with the mouse in the
B1900d-cockpit?
Cheers
Heiko
> Hi guys.
> Is there any interest in mouse acceleration properties,
> besides myself ?
> I,ve added it locally , and have mouse drag pedestal
> control
Hi guys.
Is there any interest in mouse acceleration properties, besides myself ?
I,ve added it locally , and have mouse drag pedestal controls in the Aerostar .
The calculation is already done in the code, FGMouseInput.cxx , so
I've simply written each to a property:
At line 317:
if (x != m.x
19 matches
Mail list logo
