On Friday, August 09, 2013 15:47:57 Curtis Olson wrote:
> For a work project I ended up modifying a qt program (C++) to talk to the
> FlightGear interface. I pulled in the plib socket routines and used those,
> mostly because I was unaware of/unfamiliar with the qt socket routines. My
> approach
For a work project I ended up modifying a qt program (C++) to talk to the
FlightGear interface. I pulled in the plib socket routines and used those,
mostly because I was unaware of/unfamiliar with the qt socket routines. My
approach maybe wasn't quite as clean as doing everything in already
avail
On Friday, August 09, 2013 13:21:45 James Turner wrote:
> Qt sockets are very thin wrappers around BSD / Windows sockets. More likely
> to be a character set / encoding issue? Remember you need to be explicit
> about encoding when going from 8-bit representation to a QString.
>
> That said I've no
On 9 Aug 2013, at 10:59, Adrian Musceac wrote:
> I'm writing an application which uses a socket to connect to Flightgear's
> telnet interface, and I have encountered the following issue:
> Writing to Flightgear is fine, but while reading the socket, some properties
> have weird values, and som
Hi all,
I'm writing an application which uses a socket to connect to Flightgear's
telnet interface, and I have encountered the following issue:
Writing to Flightgear is fine, but while reading the socket, some properties
have weird values, and some characters are getting replaced (L is sometime
Dear FlightGear Team,I have recently downloaded FlightGear, and am enjoying it,
but I seem not be able to download some aircraft. Even when the program says I
have downloaded the aircraft correctly, when I go to use the aircraft, it comes
up with a small blue and yellow plane. Also, with the pla
6 matches
Mail list logo
