-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Breidenbach a écrit :
>> 1) test the patch at home, to check it works
>
>
> The patch is preliminary and does NOT work well enough to commit. The
> hex tiling artifacts are unacceptable and I'd love to get an insight as
> to what might be causin
On Tue, Dec 13, 2005 at 05:15:16PM +0100, David Philippi wrote:
> Am Dienstag, den 13.12.2005, 17:08 +0100 schrieb Nils Kneuper:
> > It is mainly need on big screens and most users that
> > use big screens also do have rather fast machines. (>500MHz)
>
> Why not make it even simpler - only active
> I'll do tomorrow.
Many thanks!
Best regards
Nicolas
On Tuesday, 13 December 2005 20:02, Nicolas Weeger wrote:
> Hum, could someone more knowledgable than me merge the files please? I'm
> afraid of doing it wrongly :)
> Files ai_python.[cpp|h] from the wesnoth-python branch.
>
> The AI will need a way to know what script to call, though - gonna try
>
Hum, could someone more knowledgable than me merge the files please? I'm
afraid of doing it wrongly :)
Files ai_python.[cpp|h] from the wesnoth-python branch.
The AI will need a way to know what script to call, though - gonna try
to mess with that asap, probably a new WML tag.
Nicolas
On Tuesday, 13 December 2005 19:42, Nicolas Weeger wrote:
> So should Python support be merged to trunk?
Sure.
> Note that we can probably merge it, test it, and if not stable enough
> for release, just disable it - shouldn't be any side effect.
Ok.
--
Isaac Clerencia at Warp Networks, http://ww
> Well, 1.1 could be the perfect way to get that testing we need. As long as it
> doesn't "interfere" when "no python stuff" is loaded, it should be ok to
> release with it and let some users start doing some interesting stuff with
> it.
Hello.
So should Python support be merged to trunk?
Note
Am Dienstag, den 13.12.2005, 18:56 +0100 schrieb Isaac Clerencia:
> > Why not make it even simpler - only active it for a defined resolution
> > and above? I think everything beyond 1024x786 or even 800x600 may use
> > bilinear as it is unlikely that the user is running a very slow machine.
> It ma
On Tuesday, 13 December 2005 17:15, David Philippi wrote:
> Am Dienstag, den 13.12.2005, 17:08 +0100 schrieb Nils Kneuper:
> > It is mainly need on big screens and most users that
> > use big screens also do have rather fast machines. (>500MHz)
>
> Why not make it even simpler - only active it for
1) test the patch at home, to check it works
The patch is preliminary and does NOT work well enough to commit. The
hex tiling artifacts are unacceptable and I'd love to get an insight as
to what might be causing it.
--Jeff
I think this plan is fine with the caveat that since this might significantly
effect performance on low end machines, when you commit, make sure to email the
dev-list. It does point to the question of do we have any dedicated low-end
testers who can complain quickly if there is a performance hit?
> Hmm, maybe it would be possible to implement this via an option in the
> graphics menu? This way we would have no problem if it really is a
> little slower. It is mainly need on big screens and most users that
> use big screens also do have rather fast machines. (>500MHz)
> When we make it an opt
Am Dienstag, den 13.12.2005, 17:08 +0100 schrieb Nils Kneuper:
> It is mainly need on big screens and most users that
> use big screens also do have rather fast machines. (>500MHz)
Why not make it even simpler - only active it for a defined resolution
and above? I think everything beyond 1024x786
Hmm, maybe it would be possible to implement this via an option in the
graphics menu? This way we would have no problem if it really is a
little slower. It is mainly need on big screens and most users that
use big screens also do have rather fast machines. (>500MHz)
When we make it an option the us
This seems like a GOOD idea
On Tue, 13 Dec 2005 [EMAIL PROTECTED] wrote:
> > On Mon, Dec 12, 2005 at 09:51:29 -0600,
> > Bruno Wolff III <[EMAIL PROTECTED]> wrote:
> >>
> >> The simplest solution may be to have the campaign server stick the
> >> license
> >> message (which is already there) int
> On Mon, Dec 12, 2005 at 09:51:29 -0600,
> Bruno Wolff III <[EMAIL PROTECTED]> wrote:
>>
>> The simplest solution may be to have the campaign server stick the
>> license
>> message (which is already there) into a file in the campaign (probably
>> campaign_name/COPYING). Different campaign server
On Mon, Dec 12, 2005 at 09:51:29 -0600,
Bruno Wolff III <[EMAIL PROTECTED]> wrote:
>
> The simplest solution may be to have the campaign server stick the license
> message (which is already there) into a file in the campaign (probably
> campaign_name/COPYING). Different campaign servers could ha
On Tue, 13 Dec 2005 2:08 am, [EMAIL PROTECTED] wrote:
1) please patch against trunk, such a change will not go in the stable
branch
Ok
2) what is the performence hit of the patch ?
Unmeasured. My wimpy 1Ghz VIA CPU runs it ok even with compiler
optimization turned off.
3) please submit
>
> Here's a shorter implementation. I'm still confused
> as to what is causing the artifact on the hex tiles.
> Patch is against wesnoth 1.0.2.
>
I can't test the patch right now, just a couple of things
1) please patch against trunk, such a change will not go in the stable branch
2) what is the
Here's a shorter implementation. I'm still confused
as to what is causing the artifact on the hex tiles.
Patch is against wesnoth 1.0.2.
-Jeff
diff -u /ramdisk/home/knoppix/bar/wesnoth-1.0.2/src/sdl_utils.cpp.orig
/ramdisk/home/knoppix/bar/wesnoth-1.0.2/src/sdl_utils.cpp
--- /ramdisk/home/kno
I'm playing Wesnoth fullscreen on a 1920x1200 pixel display, and the
smaller maps do not look very good due to the use of nearest neighbor
image interpolation. This preliminary patch towards bilinear
interpolation helps. The patch basically works, except that a hex edge
tiling artifact is introduc
Hi everybody!
It would be nice if everybody could try to make sure that the credits
for his/her part are up to date. I think that currently several
contributors are missing ingame and/or in the wiki.
So please try to make sure that everyone is listed at both places. I
already wrote a mail to all tr
22 matches
Mail list logo
