On Mon 19 Mar 2007 (18:07 -0700), Don A. Hanlen wrote:
> On Mon, 19 Mar 2007, Jim Segrave wrote:
>
> > > GNUBG caused an invalid page fault in
> > > module LIBGTK-0.DLL at 0177:6dcf443c.
> > > Registers:
> > > EAX=0001 CS=0177 EIP=6dcf443c EFLGS=00010202
> > > EBX=b415 SS=017f ESP=00f6b1d0
On Mon, 19 Mar 2007, Jim Segrave wrote:
> > GNUBG caused an invalid page fault in
> > module LIBGTK-0.DLL at 0177:6dcf443c.
> > Registers:
> > EAX=0001 CS=0177 EIP=6dcf443c EFLGS=00010202
> > EBX=b415 SS=017f ESP=00f6b1d0 EBP=00f6b1e8
> > ECX=00f87040 DS=017f ESI=010e5a80 FS=59d7
> > EDX=0
On Sun 18 Mar 2007 (18:37 -0700), Don A. Hanlen wrote:
>
> hmmm, should I be CCing this to bug-gnubg?
>
> On Sun, 18 Mar 2007, Jim Segrave wrote:
>
> > For appearance, you could always export a set of board images as .png
> > files, then use a Tkinter Canvas to create a board. The png names
hmmm, should I be CCing this to bug-gnubg?
On Sun, 18 Mar 2007, Jim Segrave wrote:
> For appearance, you could always export a set of board images as .png
> files, then use a Tkinter Canvas to create a board. The png names are
> quite straightforward, so representing any board position shoul
On Fri 16 Mar 2007 (14:40 -0700), Don A. Hanlen wrote:
>
> I really appreciate you guys communicating with me on this. I was hoping
> to be spared the task of writing a board for my application. Oh well.
> I've just about got a not-so-nice Tkinter widget completed that'll work
> for me! It ki
I really appreciate you guys communicating with me on this. I was hoping
to be spared the task of writing a board for my application. Oh well.
I've just about got a not-so-nice Tkinter widget completed that'll work
for me! It kinda makes you shudder to look at it after the nice gnu board
tho.
Øystein O. Johansen wrote:
>> (In truth, the deviations from modularity are a bit surprising...)
>
> Yes, there is some kind of mess in the code. And the deviations from
> modularity is really annoying. (I've tried to refactor some thing in GNU
> Backgammon, but every time I end up *sigh* thinki
>(In truth, the deviations from modularity are a bit surprising...)
Yes, there is some kind of mess in the code. And the deviations from modularity
is really annoying. (I've tried to refactor some thing in GNU Backgammon, but
every time I end up *sigh* thinking it's too much work)
What if w
LOL Oystein. I just downloaded the C source for gnubg. It *might* be
smart but I agree it ain't simple. Lemme stare at it for a bit. I'm not
sure I'm man enough for it either! Any women out there?
(In truth, the deviations from modularity are a bit surprising...)
--
Don Hanlen
On Tue, 13
Jonathan Kinsey wrote:
What would be cool is if all the display code was totally separate with
a fixed interface and the 2d/3d (and text) display just used this
interface. I'm not sure this is even possible, but in theory it would
make it more reusable...
As a gtk custom widget with signals an
Thanks for the reply, Jonathan Kinsey.
You describe an interesting project (more than what I had in mind). Yes,
I'd think it would be desirable and useful to have the board display
separate, and yes, anything using it would be open source. To tackle it,
I'd need to know:
> Where's the pyth
I guess anything is possible... The display code is reasonably separate
but it relies on the data structures in gnubg, this is all in C code so
I imagine it would be tricky to use in a python app.
It's all covered by the GPL, so I think this means that your program
would have to be open source as
I'd like to use the gnu BG board in a python application (GUI). ...save
time programming something I can't do as well anyway with Tkinter. Is
this possible?
--
Don Hanlen
___
Bug-gnubg mailing list
Bug-gnubg@gnu.org
http://lists.gnu.org/mailman/lis
13 matches
Mail list logo
