Re: [documancer] CVS - Invalid toolbar bitmap on Windows?

[Kevin O. <ke...@tu...>]

Hi Vaclav,

On Oct 6, 2004, at 8:59 AM, Vaclav Slavik wrote:

> Hi,
>
> Kevin Ollivier wrote:
>> Were some new icons added to the Documancer package recently?
>
> Depends on your definition of "recently". Refresh and Stop icons were
> added since 0.2.3, but I didn't touch CVS in a month or so.

Wow, I believe I just found a nasty bug in wxMSW. I went to check the 
refresh and stop icons to see if there was something wrong that would 
cause them not to appear, and I noticed that they weren't in my 
Documancer source tree at all. Checking more, it appears 
src/data/refresh.png and src/data/stop.png are not actually in the 
Documancer CVS tree. (They aren't showing up in SF's CVS browser 
either.) But the amazing part here is that wxMSW doesn't even complain 
that the files don't exist! That's why I'm getting the invalid tool 
button bitmap error inside of wxToolbar::Realize().

If this is indeed the case (that wxBitmap doesn't even assert for 
nonexistent files) then I think we need to remedy that before 2.6. I'm 
going to check the source code for wxBitmap on MSW later and see if I 
can figure this out.

>> just checked out CVS HEAD and I am testing against 2.5.2.8 on
>> Windows, and whenever I try to start the program, I get an assert
>> saying "invalid tool button bitmap" in src/msw/tbar95.cpp line 635.
>
> I thought wxPython would output backtrace to stderr, does it not?

Yes, but I'm not set up for email on my Windows machine, and I was 
admittedly too lazy to create a file and copy it over the network to my 
Mac. ;-) In any case, I didn't think it mattered because the actual 
call that caused the traceback was toolbar.Realize() and it doesn't 
give any info about what bitmap caused the error exactly. (See above 
for why.)

Thanks,

Kevin