This should bring it up to about the state of the patches and comments in
ticket #1073, without the threaded device detection. Timeout is 500ms, that
should be enough to detect a LAN device, and doesn't delay startup too much.
Port r8447 plus the fixes for it in r8449, r8453, r8455 and r8456 to trunk.
git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@8460 4a71c877-e1ca-e34f-864e-861f7616d084
* You can now repair allied units.
* You can now repair allied structures.
* You can now upgrade allied structures.
* You can now rearm VTOLs on allied rearming pads.
* You can now repair your units at allied repair facilities.
* You can now guard allied units (trucks, sensors, and commanders) and structures.
* You get a selection cursor when mousing over LasSat, to make it clearer that it's selectable.
* You get the OBSERVE cursor for attack-move, the EMBARK cursor for unload transport, etc.
* A few other minor cursor fixes. Cursors should now reflect what happens when you click on them significantly more of the time.
* Clicking on a transport with no cyborgs selected will select the transport, instead of doing nothing.
* You can attack (and actually damage) your own units/structures with Alt+click, now. Still doesn't work with LasSat, to prevent backstabbing allies by moving an expendable unit into their base. For the same reason, Alt+click only works on your own units, not on your allies'.
* Alt+click works on Mac OS X now.
git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@8433 4a71c877-e1ca-e34f-864e-861f7616d084
Every call to it is saveguarded by calls to CoordInRadar, which uses almost the
same code (exactly the same until r7458). So now the calculation in
CoordInRadar is changed to be the same as in CalcRadarPosition, and
CalcRadarPosition doesn't check anymore. Fixes#1069.
git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@8401 4a71c877-e1ca-e34f-864e-861f7616d084
- Changed sound_InitLibrary so it would present all available devices to the debug and dump logs before trying to activating one of them.
- Added successfully opened device name to the debug and dump logs.
git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@8328 4a71c877-e1ca-e34f-864e-861f7616d084
- vc2k8 project is using modern style icon instead of obsolete one.
- Removed sqlite3 dependencies from vc2k5 solution.
- Set eol-style to native for iniparser.vcproj
git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@8326 4a71c877-e1ca-e34f-864e-861f7616d084
low pings (green light) is from 0-200 (was 0-600!)
medium pings (yellow light) is from 400-1000 (was 600-1200!)
high pings (red light) is from 1000-2000. (was 1200-2000)
git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@8323 4a71c877-e1ca-e34f-864e-861f7616d084
fonts.conf.wd_enable is the one where windows directory is enabled.
fonts.conf.wd_disable is the one where the windows directory is disabled (default)
The reason for this is, when enabled, it takes a very long time to build the font cache on vista & win7.
Closes ticket:1013
git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@8321 4a71c877-e1ca-e34f-864e-861f7616d084
This is used to differentiate LOG_ERROR (which is a *non* fatal error, but a error none the less) and fatal errors which result in program termination with no *visible* output (on windows/macs) on our end because of the crappy GUI functions so we usually dump it to stderr.txt and there is no clue that the program had to exit for whatever reason.
Hopefully, this will be helpful to windows people so they can differentiate between *our* exit/abort routines, and crashes that occur in drivers which look exactly the same since they get dumped back to the desktop with no visible clue why.
LOG_FATAL is *always* on in both debug & release builds.
On LOG_FATAL debug lines, on windows, we now throw up a modal dialog box with the current error message. At this time, this only happens when we have a error, and we use abort() right after the error, which makes it fatal.
That explains why this touches ~60 files :)
git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@8320 4a71c877-e1ca-e34f-864e-861f7616d084
Christian Ohm
Per Inge Mathisen
Guangcong Luo
i-nod
René Jürgens
Buginator