Void Linux discussion
 help / color / mirror / Atom feed
From: Donald Allen <donald...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Missing expansion arrows in gtk+3 tree view
Date: Wed, 16 Sep 2015 10:05:43 -0700 (PDT)	[thread overview]
Message-ID: <b38ba835-3326-4350-8791-798ec5224485@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1300 bytes --]

I have written a personal finance manager (which I call Newcash and which I 
will be releasing on github as soon as I finish the documentation). It is 
gtk+3-based and makes use of gtk's treeview to display the tree of 
accounts. This display normally has little arrows to the left of expandable 
accounts (those accounts in the tree with children). It works correctly on 
Arch Linux, Linux Mint, OpenBSD, FreeBSD and I may have forgotten something 
on which I've tested it. The arrows are missing when I run the application 
on a newly installed Void system. Clicking in the area of the missing 
arrows does expand the account, so that functionality works, but the lack 
of the display of those little icons is unacceptable. I suspect it's due to 
the font chosen by default, but that's pure speculation on my part. And 
anticipating a question, yes, I did completely rebuild my application 
having installed Void's gtk+3 and gtk+3-devel packages.

I really like some of the ideas behind void (particularly the non-use of 
systemd), but it feels like it's not quite ready for prime time. I realize 
that putting a Linux distribution together is a huge amount of work 
involving a gazillion details and so I'm not surprised that Void feels as 
if it's not quite there yet, given its relative youth. 

[-- Attachment #1.2: Type: text/html, Size: 1346 bytes --]

             reply	other threads:[~2015-09-16 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16 17:05 Donald Allen [this message]
2015-09-16 18:50 ` Duncaen
2015-09-16 20:48   ` Donald Allen
2017-04-25 14:30     ` Martin Brodbeck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b38ba835-3326-4350-8791-798ec5224485@googlegroups.com \
    --to="donald..."@gmail.com \
    --cc="void..."@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).