Re: building abicocoa from HEAD

From: <msevior_at_physics.unimelb.edu.au>
Date: Tue Sep 21 2004 - 07:15:06 CEST

>
> James Whitwell wrote:
>
>>
>>
>> On 21/09/2004, at 7:10 AM, J.M. Maurer wrote:
>>
>>>
>>> On ma, 2004-09-20 at 23:06 +0200, J.M. Maurer wrote:
>>>
>>>>> /Users/jams/src/abiword/abicocoa/abi/src/af/xap/cocoa/
>>>>> xap_CocoaDlg_Image.mm: In member function `void
>>>>> XAP_CocoaDialog_Image::event_Ok()':
>>>>> /Users/jams/src/abiword/abicocoa/abi/src/af/xap/cocoa/
>>>>> xap_CocoaDlg_Image.mm:45: error: `setAlt' undeclared (first use this
>>>>
>>>> [...snip...]
>>>>
>>>>> /Users/jams/src/abiword/abicocoa/abi/src/af/xap/cocoa/
>>>>> xap_CocoaDlg_Image.mm:242: error: `getAlt' undeclared (first use this
>>>>> function)
>>>>
>>>>
>>>> Replace setAlt with setDescription everywhere
>>>>
>>>
>>> ... and getAlt with getDescription ofcourse..
>>
>>
>> cool, figured those ones out. :) Now I get an executable that runs,
>> but the Command key doesn't work, and typing text into a document is
>> really slow (maybe timed to the cursor flashing?) Any ideas?
>>
>> thanks,
>> ;) james.
>>
>>
>>
>
> This may be the command key issue you're describing:
> http://bugzilla.abisource.com/show_bug.cgi?id=7052
>
> And the slow typing is a known issue:
> http://bugzilla.abisource.com/show_bug.cgi?id=6881
>

It would really help us if you could put a bit of time into debugging the
slow typing issue.

Are you familiar with gdb or some other OSX debugger?
If so read on!

First off cvs update your tree.
Then reconfigure with ./configure --enable-debug

then run run abiword in the debugger

(gdb AbiWord-2.2 in an xterm)

Load a document with some text, put your caret in the middle of some text
then place a break point here..

ap_EditMethods.cpp:4917

 this is the first of the following three lines

4917-> ABIWORD_VIEW;
        pView->cmdCharInsert(pCallData->m_pData, pCallData->m_dataLength);
        return;

single step through cmdCharInsert with "next"

when you get to the following return statement

print the following..

pView->getGraphics()->getPaintCount()

What do you get? If we don't get 0 we know that there is a mismatched
GR_Painter somewhere.

If you do then it's sign the OSX graphics class is being hung up somewhere.
We need to find out why it's hung up and how to fix it.

I often hang out on #abiword onthe IRC gimpnet network.

Feel free to drop by and maybe we can do some interactive debugging.

This bugs has been holding up OSX for about 5 months. We should get it fixed.

Cheers

Martin

> Hope that helps.
>
Received on Tue Sep 21 07:14:50 2004

This archive was generated by hypermail 2.1.8 : Tue Sep 21 2004 - 07:14:51 CEST