Op maandag 15 februari 2021 10:58:20 CET schreef Explorare:
> I followed the instructions on /gnucash-on-windows but failed with error
> "TypeError: can only join an iterable". And there is a warning before this:
> "libtool: warning: '../lib/libosp.la' has not been installed in
> '/c/gcdev64/
Hi,
In bug 798109 it was highlighted that the widget I wrote back in 2012 does
not respond to keyboard use well which I think would be relatively easy to
fix and maybe a couple of tweaks.
Geert suggested that it could be dropped in favour of a traditional
GtkComboBox.
The reason I wrote it was t
Hi Robert
The reality is that you're probably the most skilled in gtk in here so your
view is likely the best one. However I agree that replicating gtkcombobox
is probably unnecessary.
My personal view is that tooltips are an obscure mechanism to display
additional (occasionally crucial) useful i
Hi Bob,
I did some experiments and I agree with you it would be hard to implement this
in Gtk3 because the tooltips should be added to the internal GtkMenu. The
GtkCombobox interface does not provide access to that widget.
So there is a trade-off to make here between maintenance burden and adde
Sorry, it's AQBanking 6.2.6. I've fixed the wiki page and added links for macOS
and flathub users to the exact version of GnuCash they need.
There's no 4.4.1: We changed to a two-digit versioning system 4 years ago.
However the all-in-one bundles on macOS and Windows can have suffixes as do
fla
I generally agree, but I think that there's no great benefit to listing the
available options in most cases. The user can easily enough click the revealer
to see them. I also don't think that we want dissertation-length tooltips. If
that much verbiage is required then it should be in the help do
Thanks. I'm fine with the dropping value listings in tooltips as well. The
only reason I considered them was for the cases where per-value extra info
would be needed. In my quick evaluation of a number of them that doesn't
really seem necessary.
Regards,
Geert
Op dinsdag 16 februari 2021 17
The way we manage program help has four serious problems:
1. It's separate from the program--not even in the same git repository--so
changes to the program are seldom reflected in the help. Very little of it has
been touched in the last 10 years.
2. It's largely monolithic which makes it resist
Am 16.02.21 um 18:21 schrieb John Ralls:
> The way we manage program help has four serious problems:
>
> 1. It's separate from the program--not even in the same git repository--so
> changes to the program are seldom reflected in the help. Very little of it
> has been touched in the last 10 ye
> On Feb 16, 2021, at 4:16 PM, Frank H. Ellenberger
> wrote:
>
> Most of the static part of the GUI is in the glade files, which are XML.
> It should not be very hard to XSLT the nodes for the structure, and
> finally labels and tooltips.
Dunno about most. There's a surprising amount of hand
10 matches
Mail list logo
