Complete.Org: Mailing Lists: Archives: freeciv-dev: March 2005:
[Freeciv-Dev] Re: (PR#12430) xaw client not starting up
Home

[Freeciv-Dev] Re: (PR#12430) xaw client not starting up

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
Subject: [Freeciv-Dev] Re: (PR#12430) xaw client not starting up
From: "Vijay Kiran Kamuju" <infyquest@xxxxxxxxx>
Date: Sun, 6 Mar 2005 22:11:55 -0800
Reply-to: bugs@xxxxxxxxxxx

<URL: http://bugs.freeciv.org/Ticket/Display.html?id=12430 >

can you please test it on windows?

with cygwin and without cygwin

did u compile on linux for xaw-client

i'll also test it and if it works on it, 

i'll post the bug to cygwin-x mailing list

bye,
Vijay

On Sat, 5 Mar 2005 04:40:03 -0800, Egor Vyscrebentsov <evyscr@xxxxxxxxx> wrote:
> 
> <URL: http://bugs.freeciv.org/Ticket/Display.html?id=12430 >
> 
> On Fri, 4 Mar 2005 09:40:03 -0800
> "Jason Short" <jdorje@xxxxxxxxxxxxxxxxxxxxx> wrote:
> 
> JS>Vijay Kiran Kamuju wrote:
> JS>> Encodings: Data=UTF8, Local=ISO-8859-1, Internal ISO-8859-1
> JS>> X Error of failed request:  BadMatch(invalid parameter attributes)
> JS>> Major opcode of failed request:  93 (X_CreateCursor)
> JS>> Serial number of failed request:  5234
> JS>> Current serial number in output stream: 5238
> JS>>
> JS>> after analysis with insight on cygwin
> JS>>
> JS>> it is crashing in the for loop after load_cursors and
> JS>> InitializeActions, when i=0
> JS>> just after we assign the sprite
> JS>
> JS>I wrote this code but never tested it.  Some things to check:
> JS>
> JS>* Does get_cursor_sprite() return NULL?  The cursors can't be loaded
> JS>until after the tileset is loaded.
> 
> JS>* Does XCreatePixmapCursor expect a bitmap (monochrome image) rather
> JS>than a pixmap?
> 
> Xlib manual says that XCreatePixmapCursor is used to create cursor from two 
> bitmaps.
> It also says that this function can generate BadAlloc and BadPixmap errors.
> 
> BTW, it seems, that cursors are loaded normally on my linux mashine (CVS HEAD 
> today,
> 30 mins ago, with patch from #12111). (Not that i have tested it under 
> windows...)
> 
> Thanks, evyscr.
> 
>





[Prev in Thread] Current Thread [Next in Thread]