On Sun, Apr 24, 2011 at 6:36 AM, buginator buginato...@gmail.com wrote:
Unless there are any objections, I plan to demote ASSERT_FAILURE() to
use LOG_INFO instead of LOG_ERROR.
The main reason for this is that LOG_ERROR is meant for serious
errors, and all LOG_ERRORs are echoed to the in game
The attempt to do a partial merging of Qt branch into master ran into
some problems that required major surgery of master in order to work.
The question was posed if we should be spending so much time fixing up
master, when we could just be focusing our efforts on making the Qt
branch work
24.04.2011 10:04, Per Inge Mathisen wrote:
* The new map renderer should use shaders, but not require as much
hardware as the current. Consider this statement ironical? Only if you
have made a habit out of thinking that poor drivers mean weak
hardware. But lots of recent weak/cheap hardware
#2661: Hosting when 2100 port is not able to receive hangs the game
-+
Reporter: j0shdrunk0nwar | Owner: Cyp
Type: bug |Status: new
Priority: normal |
On Sunday, 24 April 2011 at 10:04, Per Inge Mathisen wrote:
This will have some consequences, like not being able to aim for a
stable release from master in a while,
I've wondered if the concept of stable release is actually useful for us.
Looking at 2.3, it seems to languish mostly, while
#2662: Change tickets with needinfo resolution to can't replicate this issue
without more information.
---+---
Reporter: cybersphinx | Owner: Fastdeath
Type: to-do (no feature requests!)
#2663: Confused truck (pathfinding problem)
--+-
Reporter: cybersphinx | Owner:
Type: bug |Status: new
Priority: normal | Milestone: unspecified
Component: other|
On 24/04/11 08:04 AM, Per Inge Mathisen wrote:
* We need a way for users to convert old maps to the new format. I
will write a command-line app to do it, and Fastdeath has offered to
set up a php service for it, using that app.
* Once a new map format is ready, we can start experimenting
On Sun, Apr 24, 2011 at 2:13 PM, Safety0ff safety0ff@gmail.com wrote:
Last time I checked, for Qt widgets to work properly on all platforms
with Opengl we need to use a qgraphicsview and a qglwidget subclass, and
set the glwidget as the background for the graphics view (like this:
On Sun, Apr 24, 2011 at 12:43 PM, Christian Ohm chr@gmx.net wrote:
I've wondered if the concept of stable release is actually useful for us.
It is useful for users.
We should definitely aim for quicker releases later on. Not really
sure how to do this. I think this is mostly dictated by
#2664: Rendering cleanup
+-
Reporter: Safety0ff | Owner:
Type: bug|Status: new
Priority: normal | Milestone: unspecified
Component: other | Version: unspecified
On 4/24/11, Kreuvf kre...@warzone2100.de wrote:
One thing is missing: a map editor. A new map format is of little value
without
an appropriate map editor or in other words: people need to be able to
switch to
the new format.
The only map editor that we have anyone maintaining is flaME.
So we
On Apr 24, 2011, at 3:19 PM, buginator wrote:
One thing is missing: a map editor. A new map format is of little value
without
an appropriate map editor or in other words: people need to be able to
switch to
the new format.
The only map editor that we have anyone maintaining is flaME.
On 4/24/11, Christian Ohm chr@gmx.net wrote:
On Sunday, 24 April 2011 at 10:04, Per Inge Mathisen wrote:
This will have some consequences, like not being able to aim for a
stable release from master in a while,
I've wondered if the concept of stable release is actually useful for us.
On 4/24/11, Per Inge Mathisen xxx...@gmail.com wrote:
On Sun, Apr 24, 2011 at 6:36 AM, buginator xxx...@gmail.com wrote:
Unless there are any objections, I plan to demote ASSERT_FAILURE() to
use LOG_INFO instead of LOG_ERROR.
The main reason for this is that LOG_ERROR is meant for
On 24/04/11 07:34 PM, dak180 wrote:
While it might be the only one currently maintained there is also:
https://github.com/dak180/WZME
If someone wants to resurrect it.
Unless you just want the UI layout, I wouldn't waste my time on it.
___
On Sun, Apr 24, 2011 at 9:47 PM, buginator buginato...@gmail.com wrote:
In short, we have asserts that fire, and we *know* there is a issue,
but can't get at that issue for multiple reasons. No need to spam the
in-game console with assert messages.
Then stop sending LOG_ERROR to the console?
#2665: master-qt merge
-+-
Reporter: Buginator | Owner:
Type: patch (an actual patch, not a |Status: new
request for one) |
#2666: miniupnp breaks non-debug compiles
-+-
Reporter: Per | Owner:
Type: bug |Status: new
Priority: normal | Milestone: unspecified
Component: other | Version:
Build status: FAILURE
Buildslave for this Build:bot-fast-amd64-1
Complete logs for all build steps:http://buildbot.wz2100.net/builders/master-nightly/builds/133
Build Reason:The Nightly scheduler named 'timer_master' triggered this build
Build Source Stamp:HEAD
Blamelist:
Detailed log of last
Build status: FAILURE
Buildslave for this Build:bot-fast-amd64-1
Complete logs for all build steps:http://buildbot.wz2100.net/builders/qt-nightly/builds/52
Build Reason:The Nightly scheduler named 'timer_qt' triggered this build
Build Source Stamp:HEAD
Blamelist:
Detailed log of last build
On Apr 24, 2011, at 6:43 AM, Christian Ohm wrote:
I've wondered if the concept of stable release is actually useful for us.
Looking at 2.3, it seems to languish mostly, while people work on new stuff.
So, proposal for a more git-like workflow:
-1. Get master into a reasonably stable
On Apr 24, 2011, at 3:40 PM, buginator wrote:
* We merge Qt branch into master immediately.
No objections from me.
Right, that is mostly what we do, or have done in the past, is it not ?
The issue(s) are that we have no good way to test things, and things
slip through the cracks.
On Apr 24, 2011, at 6:43 AM, Christian Ohm wrote:
I've wondered if the concept of stable release is actually useful for us.
Looking at 2.3, it seems to languish mostly, while people work on new stuff.
So, proposal for a more git-like workflow:
-1. Get master into a reasonably stable
24 matches
Mail list logo
