On 16.08.2008, at 02:12, Evan Laforge wrote: > On the cursor side, I guess this means there's no way to get the > current cursor?
No, none that I know of. It should be possible to implement that though. > As far as the guide, any argument about adding: > > - remove the bit about tabs, and say "indents are two spaces, tabs are > not allowed" > > - 80 column max for lines I would be happy with both. It was probably put in to avoid having to reformat a lot of source code ;-) > I'm all in favor of improving fltk2 rather than fltk1 if it represents > the future. But does it really? Is there any kind of timeline for > when that's going to happen? My impression is that it's been many > years. Maybe I should be asking how I can help with fltk2 then even > though I've never used it? I might if I had some confidence that it > was going to come out of "testing" any time soon, like I might have > used it if I had any such confidence. So what this says to me is "no, > don't fix anything, wait until we've got this new thing out, which > should be any year now". So that's not very encouraging. FLTK2 has never been out of the testing phase. > Speaking of not very encouraging, I have a STR #1952 which has been > open for quite a while now. It's a pretty serious bug, with a pretty > easy fix, but there hasn't been any sign that anyone actually reads > the reports. I know there's definitely interest in encouraging new > contributors, so this seems to be sending mixed messages. Does > someone with mac knowledge feel like taking a look? I have seen your repport and verified the issue. We have close the FLTK1.1 brabch alltogether, so we will not be fixing anything here anymore, with 1.1.9 beeing the latest version. Should a serious reoccuring crash bug show in 1.1.9, I may have to release 1.1.10, but I would really like to avoid that and get forces going on 1.3.0 (yes, we abandoned 1.2). >> Which also explains the tabulator chaos. We did agree on two spaces >> per indent at least. If we now manage to agree on how amny spaces are >> in a tab, we will be fine ;-). > > Understood, any code base (especially an open source one) needs > periodic cleaning. Even if it's easy, if no one does it, it will > never happen. And it hasn't happened for many years. I would be > willing to do some of it if someone is willing to review and commit > it. I would appreciate this and certainly help you with it (patch, review, commit). The most useful version to apply a patch of that magnitude would be the current 1.3 svn version. Matthias ---- http://robowerk.com/ _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
