On Mon, Dec 23, 2013 at 8:02 AM, Chris Angelico wrote:
> On Mon, Dec 23, 2013 at 11:25 PM, Tristan Van Berkom
> wrote:
> > We don't want to be chasing down scenarios where this could possibly
> > break, so the best thing we can do is commit everything immediately
> > (you could have an asynchron
On Mon, Dec 23, 2013 at 11:25 PM, Tristan Van Berkom
wrote:
> We don't want to be chasing down scenarios where this could possibly
> break, so the best thing we can do is commit everything immediately
> (you could have an asynchronous layer in your data model which handles
> this, if performance o
On Mon, 2013-12-23 at 09:41 +, Phillip Wood wrote:
> On 16/12/13 21:27, Chris Angelico wrote:
> >
> > I have a form with a whole pile of entry fields (GTK2.Entry), and I
> > need to do some processing (and save the edit) whenever the user's
> > edited a field and is now done editing. Is there a
On 16/12/13 21:27, Chris Angelico wrote:
I have a form with a whole pile of entry fields (GTK2.Entry), and I
need to do some processing (and save the edit) whenever the user's
edited a field and is now done editing. Is there a standard way to
recognize this? I'm thinking of something like the V
