It’s because Gtk2 and Gtk3 use different paths to the accelerators. Gtk3 can
read the Gtk2 paths but not vice-versa. Because Gtk2 had the ability to change
accelerators from the menus (I think that was removed from Gtk3 but I’m not
sure, and so I haven’t changed the logic) GnuCash writes out a n
Adrien,
It’s been going on a while, and it’s still there. I am using 2.6.19 and 3.1.2.
It has something to do with how GTK3 handles accelerator keys (or something
like that). It’s mostly an inconvenience, since there is a workaround that
involves deleting a file that GTK3 creates (or something
Interesting, is this recent? I was switching between 3.0/2.6.19 and then
3.1/2.6.21 and I never noticed them change. Since moving to 3.2 I haven’t tried
a 2.6.x version again.
Regards,
Adrien
> On Aug 27, 2018, at 3:18 PM, David T. via gnucash-user
> wrote:
>
> Just note that if you use 3.x
Just note that if you use 3.x and go back to 2.6.x, the program and your data
will still work together, but your key bindings will get changed (Command-S
will be Ctrl-S, etc.). It’s a little disconcerting at first.
> On Aug 27, 2018, at 4:00 PM, John Ralls wrote:
>
> It's a personal decision b
It's a personal decision but there are only a few weeks till 3.3 so you might
wait. On the other hand since you have a Mac you have the luxury of being able
to have as many GnuCash versions as you like, just make sure that they either
have different names or are in different folders. As long as
After 20 years on a linux desktop, I find myself in an iMac. I have gnc
2.6.21 running in macOS 10.13.6. I see that I was offered the "stable" 3.2
package as a download. But it seems like I saw a lot of folks with issues
with 3.2. Should I upgrade?
Keith
___