Re: emelFM2 0.7.0 released

  • From: <tpgww@xxxxxxxxxxx>
  • To: emelfm2@xxxxxxxxxxxxx
  • Date: Fri, 20 Nov 2009 06:53:22 +1100

On Thu, 19 Nov 2009 12:11:37 -0500
Grégory SCHMITT <gy.schmitt@xxxxxxxxx> wrote:

> 2009/11/19  <tpgww@xxxxxxxxxxx>:
> > Hello all.
> >
> > Another month (or 3), another release. I decided to badge it as 0.7.x 
> > because I now find myself working with it in a different manner. The 
> > directory histories in the combo-boxes work differently now. They don't 
> > record everything opened, just the places 'activated' (by <Enter> press or 
> > double-click in the entry) so they function a bit like not-so-permanent 
> > bookmarks. One consequence of this is greater reliance on the 
> > go-forward/back menus presented upon <Control>click on the forward/back 
> > buttons in the toolbars, and now also automatically popped up if you hover 
> > the pointer over those buttons for about 2/3 second.
> >
> > I'm disappointed to report that gtk 2.18 seems to have hit us with more 
> > instance(s) of un-documented, un-protected and asynchronous usage of the X 
> > backend. Sporadically I've seen e2-session-shutdown when trying to do 
> > something that involves on-screen changes. It might be just a cd, or a 
> > dialog popup, or ... ? It doesn't happen repeatably, or often, so I've not 
> > yet been able to establish a pattern, as a basis for (yet another!) 
> > workaround of bad gtk behaviour. Hopefully feedback from a wider group of 
> > users will assist.
> 
> Using gtk 2.12, I can't compile either 0.7.0 or the svn:
> 
> objs/src/dialogs/e2_config_dialog.o: In function `e2_confdlg_extcolorpick_cb':
> e2_config_dialog.c:(.text+0x3127): undefined reference to
> `gtk_dialog_get_action_area'
> collect2: ld returned 1 exit status

Oops, missed one.

        GtkWidget *bbox = gtk_dialog_get_action_area (GTK_DIALOG(dialog));

should be

        GtkWidget *bbox =
#ifdef USE_GTK2_14
                gtk_dialog_get_action_area (GTK_DIALOG (dialog));
#else
                GTK_DIALOG (dialog)->action_area;
#endif

I'll post a replacement with this fix, ASAP.

Regards
Tom


--
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: