> Is there some sort of flag I need to set to alert Evo that a value in
> the db has changed? I'm currently calling Bonobo_ConfigDatabase_sync
> but obviously that's not all I need.
Evolution doesn't listen for changes to the db. It assumes that it's the
only thing changing anything.
-- Dan
_
On Wed, 2002-05-15 at 05:25, Michael Meeks wrote:
> Of course no-one wants to use threads, the infrastructure isn't there.
> The above scheme would have the benefit of removing a chunk of queueing
> code in evolution [ AFAIR lots of incoming CORBA calls are just defered
> to idle manually -
I have some simple code which can change values in evolution's config db
using bonobo-conf. The values do change based on queries to the db but
when I look at the UI, the value hasn't changed and in fact, any later
queries will now show the original value.
Is there some sort of flag I need to set
On Tue, 2002-05-14 at 18:00, Austin Gonyou wrote:
> Not to mention the fact that, great, I can assign labels, but now what
> can I *do* with them?
Yeah, we should add a search criterion for the category labels in the
search bar.
Jeff? :-)
--
Ettore
__
On Wed, 2002-05-15 at 08:16, Shawn Walker wrote:
> It would have been a lot easier to have a HOWTO documents that
> explains how to write a plugin for evolution. Reading the code
> isn't the best way to figure out what to do because you have to look
> at all the source code just to try to find so
On Wed, 2002-05-15 at 05:25, Michael Meeks wrote:
> Of course no-one wants to use threads, the infrastructure isn't there.
That has been said for years, and instead of spending resources to make
the libraries play nicely with threads, hacks over hacks to avoid using
threads have been built. :-)
On Tue, 2002-05-14 at 04:34, Michael Meeks wrote:
> For each corba method we add an IDL [or other] annotation that
> describes the method behavior and (re-)ordering constraints. Thus:
>
> + oneway foo (in string baa) [ handle_at_idle, no_re_enter ];
>
> Or perhaps - for people wh
> It would have been a lot easier to have a HOWTO documents that
> explains how to write a plugin for evolution.
It's one of those "copious free time" things. We could either document
the code, or fix bugs... And especially pre-1.0, there was disincentive
to document stuff, since it all kept chan
On Wed, 2002-05-15 at 18:55, Michael Meeks wrote:
> Hi Michael,
>
> On Wed, 2002-05-15 at 03:07, Not Zed wrote:
> > > It's not possible to attach gdb to a process that lives for only a few
> > > handfuls of milliseconds, and dies without giving a user visible
> > > message. Bug buddy would help
Well if you could point us to your code, we could save everyone a lot of
time.
Infact, if you could even tell us what you're working on, we mihgt be a
bit more cooperative.
This is a free software project, we've laid all our cards on the table,
expecting even more from us for free just seems, w
Jeff,
Thanks for the pointer.
It would have been a lot easier to have a HOWTO documents that explains how to write a
plugin for evolution. Reading the code isn't the best way to figure out what to do
because you have to look at all the source code just to try to find something to do
and that
Hi Michael,
On Wed, 2002-05-15 at 03:07, Not Zed wrote:
> > It's not possible to attach gdb to a process that lives for only a few
> > handfuls of milliseconds, and dies without giving a user visible
> > message. Bug buddy would help to get this error handled, that is unless
> > you know some
12 matches
Mail list logo
