On 5 August 2011 21:45, Warren Young wrote:
On 8/5/2011 2:04 PM, Andy Koppe wrote:
Which leaves the question how the icon with the 256x256 became so big.
I'd used a Cygwin build of 'icotool' from 'icoutils' for that,
icotool's --help is confusing. The magic incantation is:
$
On Aug 5 21:04, Andy Koppe wrote:
Going back to the 256x256 PNG I put into the icon though, it's
actually only 16KB, so do find that attached. Also attached is the
52KB 768x768 version exported from InkScape that I'd generated the
smaller ones from by scaling them down in Paint.net.
*grab*
On Aug 5 18:18, Charles Wilson wrote:
On 8/5/2011 8:51 AM, Corinna Vinschen wrote:
On Aug 5 13:17, Corinna Vinschen wrote:
the below patch cleans up peflags so that it uses the official Windows
types to access the COFF and PE flags via a memory map, rather than
seek/read, seek/write to
On 6 August 2011 09:28, Corinna Vinschen wrote:
On Aug 5 11:35, Warren Young wrote:
On 8/3/2011 11:49 PM, Andy Koppe wrote:
Warren's has the advantage of a 256 version and that it's more
tweakable assuming he provides the vector version it's presumably
based on.
Sorry, there is currently
Hi Chuck,
here's another simplification of peflags. The file gets opened and
closed in do_mark now. get_xxx and set_xxx get the pe_flags pointer
rather than the filename as parameter.
Ok to apply?
Corinna
* peflags.c (pe_file): Move definition to start of file.
(pe_open):
On 8/6/2011 3:25 PM, Corinna Vinschen wrote:
here's another simplification of peflags. The file gets opened and
closed in do_mark now. get_xxx and set_xxx get the pe_flags pointer
rather than the filename as parameter.
Ok to apply?
Sure, with minor changes: there are a couple of early
