Open GoogleCodeExporter opened 9 years ago
6 is done.
Original comment by thunor...@hotmail.com
on 13 Jul 2011 at 4:46
7 is started but it'll be a while as it's complicated.
Original comment by thunor...@hotmail.com
on 19 Jul 2011 at 1:42
7 is done.
5) I came across an example 09.03-tree_icon_columns that supports <input
stock_column="0"> which accepts a stock icon as the first column
(icon_column="0" also works). So you can use this:
function list() {
ifs="$IFS"
IFS=
echo $(<list)
IFS="$ifs"
}; export -f list
in combination with <input stock_column="0">list</input> or <input
icon_column="0">list</input>
Original comment by thunor...@hotmail.com
on 2 Aug 2011 at 5:50
I'm working in the lexer/parser and I've noticed that <input file> does
actually support tag attributes so <input file stock_column="0"> is possible.
Original comment by thunor...@hotmail.com
on 10 Aug 2011 at 10:22
5 is fixed. Oddly it was all in place to work but simple changes to complete it
weren't done, almost as though development had stopped and it remained
unfinished.
Original comment by thunor...@hotmail.com
on 30 Aug 2011 at 11:39
3 is done in r400 with an optional natural sort too.
Original comment by thunor...@hotmail.com
on 4 Sep 2012 at 9:11
The unnecessary exporting of variables which contain large amounts of data
should be addressed, for example an edit widget which contains a README that
doesn't require exporting but it gets exported because its variable name has
been declared -- this could possibly be dealt with by using <variable
export="false">VARIABLE</variable>.
Original comment by thunor...@hotmail.com
on 26 Sep 2012 at 3:28
Loading a null pixmap i.e. <input file>""</input> causes a segfault which is
not the best way to tell the application developer that a valid file is
mandatory. Actually I don't like the fact that it's mandatory and in the wiki
it's the sole reason why there exists a mandatory column, so get rid of this
requirement.
Original comment by thunor...@hotmail.com
on 27 Sep 2012 at 10:32
Inputting nothing into the edit widget causes a gtk+ critical message although
it doesn't cause any problems. This has been like this since at least 0.7.20
and it should be fixed consistent with other comparable widgets.
Original comment by thunor...@hotmail.com
on 27 Sep 2012 at 10:50
Fixed comment 9 issue in r469.
Original comment by thunor...@hotmail.com
on 10 Nov 2012 at 11:31
Fixed comment 8 issue in r470.
Original comment by thunor...@hotmail.com
on 11 Nov 2012 at 10:41
Fixed comment 7 issue in r473.
Original comment by thunor...@hotmail.com
on 17 Nov 2012 at 5:40
Original issue reported on code.google.com by
thunor...@hotmail.com
on 22 Jun 2011 at 11:03