Cool -- this sounds like a small list.
        BTW, how did you generate this list? (ie. search criteria)


Matthias Melcher wrote:
> Thanks to you all so much for keeping on working on the STR's. I am still 
> quite busy at work and I was no help at all. I will try to add a bit more man 
> power in the next days as I get back to coding a bit.
> 
> As you know, I tried at the beginning of the year to set 1.3.0 in stone by 
> creating a few release candidates, but bugs kept creeping in. At this point, 
> I would like to do another RC soon, seeing that there are only six bugs. So 
> here's my list:
> 
> 
> * 2500        fltk.list.in (EPM) is outdated  Config Files    New     HIGH    
> 
> Mike, will you have time to do this? If not, can we do this?
>  
> * 2597        FLUID generates wrong source code to initialize menu labels.    
>         New     HIGH     
> 
> There is a patch with this one. Can it be applied? Manolo, can you go on 
> without an .fl file? If not, I would kick this to 1.4 because the submitter 
> is not replying.
> 
> * 2614        Fl_Widget label doesn't clear it's old screen usage before draw 
> new label               New     MOD      
> 
> Can be closed.
> 
> * 2622        cannot compile on cygwin                New     MOD      
> 
> Can't say anything here... .
> 
> * 2420        Tab-Navigation focuses non-active_r() widgets   Core Library    
> Pending LOW      
> 
> Albrecht, if the user can't give us an example, we close this or push it to 
> 1.4 (which will then likely become 1.3.1 anyways)
> 
> * 2617        Inconsistent behavior for Fl_Window on win32    Core Library    
> New     LOW      
> 
> This is simple: a FL_SHOW can appear at any time. Using every FL_SHOW to 
> initialize something is wrong and can be avoided in very simple ways. We must 
> raise the window afetr the modal window is closed due to a bug in the 
> MSWindows window manager (2000 and XP, IIRC, I have stopped using MSWindows 
> after that, so I don't know if the bug's still there).
> 
> All the remaining issues are RFE's and will not keep us from doing the next 
> RC.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to