Hi all,
When Evolution on DirectFB is run the task summary , memo summary appears
black but
when click on the click-to-add it appears white as expected.
Investigating the source code has revealed that this part is formed in e*
volution-2.12/widgets/tables* e-table.c
in *e_table_setup_table()
On Fri, Jun 13, 2008 at 12:17 PM, svalbard colaco [EMAIL PROTECTED]
wrote:
Hi Milan ,
Yup i got the sources but there is nt any anti-aliasedaa
mode of canvas generation . and e_canvas are diffrent from gnome_canvases
i think.
Neither did i get a function for repainting a canavs.
Any more
Can you just point us to the right patch, that extends API ? I seem to
hit the wrong patch. I dont see any .h changes also.
Sorry for the confusion. The patch I pointed to
(http://bugzilla.gnome.org/attachment.cgi?id=112638) explains the required API
version change, not the API extension
On Fri, 2008-06-13 at 12:17 +0530, svalbard colaco wrote:
Yup i got the sources but there is nt any anti-aliasedaa
mode of canvas generation . and e_canvas are diffrent from
gnome_canvases
i think.
Neither did i get a function for repainting a
Hi Milan
Thanks for your prompt reply,
aa is not a member of the ECANVAS structure ;
In gnome_canvas_new_aa() function aa is a member of the Gnome_canvas
structure , defined as below
/* Whether the canvas is in antialiased mode or not */
unsigned int aa : 1;
And the link below gives us
On Fri, 2008-06-13 at 17:16 +0530, svalbard colaco wrote:
Thanks for your prompt reply,
aa is not a member of the ECANVAS structure ;
In gnome_canvas_new_aa() function aa is a member of the Gnome_canvas
structure , defined as below
/* Whether the canvas is in antialiased mode or not */
Greetings,
I previously posted here for help on checking the composer window text for
dirty words.
I used the attachment-reminder plugin as an example. Thanks for the suggestion.
If a dirty word is found by my plugin; is there a good way to highlight
/underline/ mark that word
in the
On Mon, 2008-05-05 at 10:58 +0530, Srinivasa Ragavan wrote:
Ross,
I had a chat with JP and He pointed me to a old README.
===
The issue was around no backwards compatability, from the old README:
In my experience recently Berkeley DB has been a lot more forgiving
recently. Note that