On Sun, Sep 2, 2012 at 3:07 PM, Gijs de Rooy wrote:
>> This is now checked in as the new Joystick Configuration item under
>> the Help menu, which replaces the Joystick Information dialog.
>
> I think you forgot to add it to the menu?
Whoops. You are correct. I'll correct that when I get the cha
Hi Stuart,
> This is now checked in as the new Joystick Configuration item under
> the Help menu, which replaces the Joystick Information dialog.
I think you forgot to add it to the menu?
I was able to open the dialog via fgcommand, and from what I've tested so far
(a very quick test with a si
On Sat, Aug 11, 2012 at 9:40 PM, Stuart Buchanan wrote:
> 2) Joystick configuration. All of the people reading this list are
> more than competent to write their own joystick XML config file, but
> it's something that I see huge numbers of posts about on the forum,
> from people who do not have eno
James Turner wrote:
> On 12 Aug 2012, at 20:44, Martin Spott wrote:
>
>>> But it's not an either/or. There could be an FGCom binary that uses the
>>> same
>>> code as the built-in FGCom.
>>
>> Which environment would be set up to build this separate binary ?
>
> The fgfs one, but I don't think
On Sun, Aug 12, 2012 at 4:48 PM, James Turner wrote:
> On 11 Aug 2012, at 22:52, Martin Spott wrote:
>>> 3) Scenery. Terrasync is now built into FG, and we have nice UI to
>>> configure it in-sim. However, it still requires users to set up a
>>> separate directory and configure FG_SCENERY before
On 12 Aug 2012, at 20:44, Martin Spott wrote:
>> But it's not an either/or. There could be an FGCom binary that uses the same
>> code as the built-in FGCom.
>
> Which environment would be set up to build this separate binary ?
The fgfs one, but I don't think that's a particularly onerous requi
Stefan Seifert wrote:
> On Sunday 12 August 2012 16:07:18 Martin Spott wrote:
>
>> Whereas there's little use of TerraSync without the FG flight sim,
>> there are plausible usage scenarios for FGCom _without_ FlightGear,
>> let's say for ATC. Therefore, while it makes sense to package FGCom
>> al
Hi James
Am 12.08.2012 um 17:48 schrieb James Turner :
>
> On 11 Aug 2012, at 22:52, Martin Spott wrote:
>
>>> 3) Scenery. Terrasync is now built into FG, and we have nice UI to
>>> configure it in-sim. However, it still requires users to set up a
>>> separate directory and configure FG_SC
On Sunday 12 August 2012 16:07:18 Martin Spott wrote:
> Whereas there's little use of TerraSync without the FG flight sim,
> there are plausible usage scenarios for FGCom _without_ FlightGear,
> let's say for ATC. Therefore, while it makes sense to package FGCom
> alongside with FlightGear for th
James Turner wrote:
> Usability was the main reason for making terrasync be available as
> in-process option, and I'm strongly considering doing the same thing
> for fgcom, although that has a few extra complications.
Whereas there's little use of TerraSync without the FG flight sim,
there are pl
On 11 Aug 2012, at 22:52, Martin Spott wrote:
>> 3) Scenery. Terrasync is now built into FG, and we have nice UI to
>> configure it in-sim. However, it still requires users to set up a
>> separate directory and configure FG_SCENERY before it can be used. It
>> would be great if the standard in
Stuart Buchanan wrote:
> 3) Scenery. Terrasync is now built into FG, and we have nice UI to
> configure it in-sim. However, it still requires users to set up a
> separate directory and configure FG_SCENERY before it can be used. It
> would be great if the standard installers created an
> $FG_RO
12 matches
Mail list logo
