Re: -draggedImageLocation giving incorrect results?

2007-04-29 Thread Michael Gardner
On 4/30/07, Richard Frith-Macdonald <[EMAIL PROTECTED]> wrote: The coordinates returned by the -draggedImageLocation method are the coordinates of the bottom left corner of the image in the base coordinate system of the window receiving the drag. That means you need to do 'dropPoint = [dropView

Re: -draggedImageLocation giving incorrect results?

2007-04-29 Thread Richard Frith-Macdonald
On 26 Apr 2007, at 14:26, Fred Kiefer wrote: Michael Gardner wrote: I've got some code in an NSImageView subclass that looks like this: -(void) mouseDown: (NSEvent*)event { ... [self dragImage: [self image] at: NSZeroPoint offset: NSZeroSize event: event pasteboard: pboard sourc

Gnustep-base thread creation bug. continued.

2007-04-29 Thread Chris Ball
I spent a bit of time looking at this today and realized that the way thr-pthead.m is initialized isn't exactly my problem. It turns out that my build of base is using gcc's primitives directly and not the thr-pthread.m here. This leaves me more confused as it looks like the gcc primitives should

Re: Gnustep-base thread creation bug.

2007-04-29 Thread Richard Frith-Macdonald
On 27 Apr 2007, at 22:56, Chris Ball wrote: Right now there appears to be a slightly subtle bug in thr-pthread.m. Specifically the threads created here are created as joinable threads, this is bad because joinable threads have to be joined before their memory is released. What we really wa

Gnustep-base thread creation bug.

2007-04-29 Thread Chris Ball
Right now there appears to be a slightly subtle bug in thr-pthread.m. Specifically the threads created here are created as joinable threads, this is bad because joinable threads have to be joined before their memory is released. What we really want here are detached threads that just go away when

Application crashes when embedding GNU Smalltalk lib - Help?

2007-04-29 Thread Tim McIntosh
Does anyone happen to know why the mere presence of "-lgst" (GNU Smalltalk library) in the link would cause the attached app to crash? (see transcript below)Thanks!-TimTranscript:% uname -aFreeBSD kashyyyk.astro.net 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007     [EMAIL PROTECT

Re: Themeing

2007-04-29 Thread Fred Kiefer
Christopher Armstrong wrote: > Fred Kiefer wrote: >> Hi Christopher, >> >> there is a small but very annoying problem with your patch for gui: You >> added some clean up of he formatting to it. Now it is great to replace >> the tab characters that went into the files with spaces. After noticing >>

Re: Themeing

2007-04-29 Thread Andrew Ruder
On Sun, Apr 29, 2007 at 09:43:26PM +1000, Christopher Armstrong wrote: > Fred Kiefer wrote: > Sorry, the reformatting is an accidental part of me writing code or > possibly my editor (I'm using VIM with tabs set to be expanded to > spaces: sw=2, cin, expandtab, ai, sta - which one do I turn off?)

Re: Themeing

2007-04-29 Thread Christopher Armstrong
Hi Turns out that svn diff command can be told to ignore whitespace changes. This patch is alot smaller and contains the useful changes. I don't know if it works. http://carmstrong.fastmail.com.au/gnustep-gui-themeing-20070429-2.diff Regards

Re: Themeing

2007-04-29 Thread Christopher Armstrong
Fred Kiefer wrote: Hi Christopher, there is a small but very annoying problem with your patch for gui: You added some clean up of he formatting to it. Now it is great to replace the tab characters that went into the files with spaces. After noticing that my editor used tabs instead of spaces for

Re: Themeing

2007-04-29 Thread Fred Kiefer
> http://carmstrong.fastmail.com.au/gnustep-gui-themeing-20070429.diff > http://carmstrong.fastmail.com.au/win32theme.tgz > > The first is a patch that should be applied against the current > gnustep-gui SVN (don't use your working copy as this patch is not by any > means com

Re: -draggedImageLocation giving incorrect results?

2007-04-29 Thread Fred Kiefer
Michael Gardner wrote: > On 4/28/07, Fred Kiefer <[EMAIL PROTECTED]> wrote: >> Do you mean 0.11 as the latest release that was still fine? The current >> release is now 0.12 and there aren't any big differences between trunk >> and that release. > > Ah, I wasn't aware that 0.12 had been released.