[STR Closed w/Resolution]
Link: http://www.fltk.org/str.php?L2935
Version: 1.3-current
Fix Version: 1.3-current (r9884)
STR 2935 applied in svn.
Thanks to Michael Baeuerle for the patch.
Link: http://www.fltk.org/str.php?L2935
Version: 1.3-current
Fix Version: 1.3-current (r9884)
___
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2935
Version: 1.3-current
Fix Version: 1.3-current (r9884)
Fixed in Subversion repository.
Link: http://www.fltk.org/str.php?L2935
Version: 1.3-current
Fix Version: 1.3-
[STR Closed w/Resolution]
Link: http://www.fltk.org/str.php?L2931
Version: 1.3-current
Fix Version: 1.3-current (r9833)
Applied the simplified version of Michael Baeuerle's scandir_posix patch.
Note that this patch does not have all the const correct goodness from the
earlier patches, but does
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2931
Version: 1.3-current
ALbrecht queried whether there are any ABI issues: Micha reports that it
looks like there are.
In particular, the change of the prototypes of th
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2931
Version: 1.3-current
Currently tested on the following systems:
--
Windows:
- WinXP with mingw32 (
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2931
Version: 1.3-current
Upload Michael Baeuerle's patches to implement a scandir() function that we
can use on *nix systems that is free of any potential license restrict
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2862
Version: 1.3-current
Link: http://www.fltk.org/str.php?L2862
Version: 1.3-current
___
fltk-bugs mailing list
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2823
Version: 1.3-current
Link: http://www.fltk.org/str.php?L2823
Version: 1.3-current
___
fltk-bugs mailing list
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2822
Version: 1.3-current
Link: http://www.fltk.org/str.php?L2822
Version: 1.3-current
___
fltk-bugs mailing list
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2802
Version: 1.3-current
Link: http://www.fltk.org/str.php?L2802
Version: 1.3-current
___
fltk-bugs mailing list
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2798
Version: 1.3-current
Link: http://www.fltk.org/str.php?L2798
Version: 1.3-current
___
fltk-bugs mailing list
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2857
Version: 1.3-current
Link: http://www.fltk.org/str.php?L2857
Version: 1.3-current
___
fltk-bugs mailing list
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2861
Version: 1.3-feature
Link: http://www.fltk.org/str.php?L2861
Version: 1.3-feature
___
fltk-bugs mailing list
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2873
Version: 1.3-current
Link: http://www.fltk.org/str.php?L2873
Version: 1.3-current
___
fltk-bugs mailing list
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2845
Version: 1.3-current
Link: http://www.fltk.org/str.php?L2845
Version: 1.3-current
___
fltk-bugs mailing list
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2730
Version: 1.3-current
Corvid indicates this arose after fixing #2691... Matt, I think that was
applied by you; do you know what is going on with this one?
The text ed
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2833
Version: 3.0
As a rider to this, I find that with judicious tweaking of the include
paths in makeinclude I can get this to build OK, so that might be a
feasible worka
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2833
Version: 3.0
Fltk-3 attempts to build the local PNG files even if configure selects the
system PNG libs instead.
However, this usually fails, since the local PNG lib
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2819
Version: 1.3-current
OK - took r9329 and applied the proposed patch "by hand".
make clean ; make proceeds normally and a brief run of a few test examples
works well.
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2819
Version: 1.3-current
Using "older" mingw - i.e. gcc-3.4.2 and Msys-1.0, and testing fltk-1.3
r9329 I find:
- The stock build proceeds correctly.
- config.h has #de
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2814
Version: 3.0
Switching to using a "knwn good" fluid (the one from my fltk-1.3 build in
this case) I now build 68 out of 70 exe's.
The hold-out (i.e. still broken) ar
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2814
Version: 3.0
Yup, probably...
If we use the "wrong" fluid (i.e. the fltk3 fluid) then, with the current
build (r9315) we get 58 out of 70 exe's built.
Almost all th
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2814
Version: 3.0
Attached file "build-log"...
Link: http://www.fltk.org/str.php?L2814
Version: 3.0
build-log
Description: Binary data
__
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2814
Version: 3.0
Helps a bit - at least on WInXP i'm now building 54 targets.
We're getting there!
Log of the current errors attached, in case anyone has time to take a
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2814
Version: 3.0
Note: log gathered on a Msys/mingw build on WinXP, for reference. I imagine
that the results will be broadly similar on other hosts, but have not (yet)
c
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2814
Version: 3.0
Attached is a build log showing the things that are not currently building
in the fltk-1.3 compatability mode.
Obtained from building in the "test1" fold
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2773
Version: 1.3-current
Any update on this?
I know Manolo did a pile of good work in sorting out how the screen and
work areas are computed, but I wonder if the effect
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2781
Version: 1.3.0
For the record, one of my test machines in ubuntu 11.10 and I am not seeing
any problems, either with the svn repo or with the weeklies, so I don't
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2797
Version: 1.3-current
Side note: This STR may also have relevance to STR 2791, where the
discussion is about what happens to Fl_Tile if you resize the window to
0x0...
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2791
Version: 1.3-feature
Note for others: this STR might be tangentially related to STR 2797, where
it turns out that if you resize a double window to 0x0 AND are not usi
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2797
Version: 1.3-current
Yup, that sounds like the best deal...
Also, why am I not getting any of these posts in my mail???
Other fltk mail seems to be arriving OK...
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2676
Version: 1.3-current
OK.
So... are we going to close this one as "not a fltk bug" and move on,
or...
Link: http://www.fltk.org/str.php?L2676
Version: 1.3-current
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2735
Version: 1.3-current
Responding to Torsten's question, I don't think other languages are likely
to be affected? The sharp-s thing is more of a Germanic languages thin
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2709
Version: 1.3.0
I can't remember - did this ever get fixed?
Link: http://www.fltk.org/str.php?L2709
Version: 1.3.0
___
f
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2771
Version: 1.3-current
Also, for the record, that's:
http://www.fltk.org/newsgroups.php?gfltk.general+v:33811
In our own archive...
And I still don't know what the
[STR Closed w/Resolution]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
Fix Version: 1.3-current (r9210)
Fixed in Subversion repository.
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
Fix Version: 1.3-current (r9210)
___
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
OK - r9210 should do it...
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
___
fltk-bugs mailing
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
OK - this is odd.
I never got any update emails form this STR, but I now see that Matt said,
on the 20th Sept., that we should try removing the code a
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2797
Version: 1.3-current
Just some additional notes culled from the ref'd thread:
It appears, based on testing by the OP (David) and by me, that the crux
may be in the F
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2738
Version: 1.4-feature
Link: http://www.fltk.org/str.php?L2738
Version: 1.4-feature
___
fltk-bugs mailing list
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2723
Version: 1.3.0
Maybe if we use tachyonic neutrinos we can fix STR's from the future...
Link: http://www.fltk.org/str.php?L2723
Version: 1.3.0
_
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2697
Version: 1.3-current
NOTE: when this is in place, it will be very useful for fixing #2695 I
think...
Link: http://www.fltk.org/str.php?L2697
Version: 1.3-current
_
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2695
Version: 1.3-current
Fix Version: 1.3-current (r8929)
NOTE: There is work in #2697 to create the necessary work_area methods
(thanks Manolo) that we should be abl
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2705
Version: 1.3-current
Albrecht - you figured out the last one, any ideas on this?
Link: http://www.fltk.org/str.php?L2705
Version: 1.3-current
_
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2697
Version: 1.3-current
Sounds good - but I don't have ready access to any multi-head kit; all my
good gear is still in storage while we work on the house (yes, and that
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
I'd be inclined to remove the suspect code, perhaps?
Then see if anybody shouts...
It seems it may be working around some historical issue that has r
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2682
Version: 1.3-current
Sorry - but I still can't figure out how to reproduce this bug, based on
your description.
Can you post a step-by-step description (maybe even i
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2709
Version: 1.3.0
Ok, checked the logs. r8630 says:
r8630 | AlbrechtS | 2011-05-01 13:45:29 +01
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2709
Version: 1.3.0
Link: http://www.fltk.org/str.php?L2709
Version: 1.3.0
___
fltk-bugs mailing list
fltk-bugs@easysw.com
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2709
Version: 1.3.0
Gents,
We should change the title of this report... It is not x64 or WIN7
specific, it's more like a general bug in fltk-1.3 on WinXX hosts...
Anyway
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2697
Version: 1.3-current
I do not know - except that we must be consistent (for whatever that
means...)
The OSX method, that returns x,y,w,h, for the focussed display, s
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2697
Version: 1.3-current
Manolo reports that the Fl::x(), y(), w() and h() functions return
different responses across platforms, in multi-head systems:
- on Mac OS, the
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2695
Version: 1.3-current
Fix Version: 1.3-current (r8929)
I don't have enough (or indeed any!) different multi-head systems to test,
but is Manolo right that the beha
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2695
Version: 1.3-current
Fix Version: 1.3-current (r8929)
Manolo,
Yes, that works OK, *for the single-monitor* case - but as you will no
doubt have noted from my ana
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2695
Version: 1.3-current
Oops - meant to say: little arrows might be a nice addition.
Link: http://www.fltk.org/str.php?L2695
Version: 1.3-current
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2695
Version: 1.3-current
The idea of adding an optional flag to the the screen_xywh calls for
WORK_AREA vs SCREEN_AREA is attractive - but there are (currently) 4
differe
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2695
Version: 1.3-current
OK, here's some more details. Albrecht and I have looked into this, and
here's some notes...
Consider fltk-1.3 r8914, in the file Fl_Menu.cxx at
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2695
Version: 1.3-current
At least on Windows, possibly others, the huge menus no longer scroll at
screen edges.
This can be seen by testing with the menubar demo. Compar
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
I've added a #warning message to the "suspect" code, in the hope that this
will let us see when/where/if it is ever actually used.
Though this will on
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2689
Version: 1.3-current
Link: http://www.fltk.org/str.php?L2689
Version: 1.3-current
___
fltk-bugs mailing list
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2686
Version: 1.3-current
Link: http://www.fltk.org/str.php?L2686
Version: 1.3-current
___
fltk-bugs mailing list
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2688
Version: 1.3-current
Hmm - that might be right... I'll try and find time to dig into this one...
Anyone else know what's going on here?
Link: http://www.fltk.org/st
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2678
Version: 1.3.0
Is there any update on this error report?
Link: http://www.fltk.org/str.php?L2678
Version: 1.3.0
___
flt
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2676
Version: 1.3-current
Is there any update on this?
Are we in a position where we can say whether this is a bug, or just a
"feature" of the OP's setup, or...?
Link:
[STR Closed w/Resolution]
Link: http://www.fltk.org/str.php?L2690
Version: 1.3-current
Fix Version: 1.3-current (r8911)
Fixed in Subversion repository.
Link: http://www.fltk.org/str.php?L2690
Version: 1.3-current
Fix Version: 1.3-current (r8911)
__
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2690
Version: 1.3-current
This looks to be correct - I might go ahead and apply it, if no one
objects?
Link: http://www.fltk.org/str.php?L2690
Version: 1.3-current
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2689
Version: 1.3-current
There's somethng a bit weird going on with the expansion of symbols, in
particualr the "@" symbol, when using fl_draw.
This was initially flagged
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2682
Version: 1.3-current
can you bring this discussion onto fltk.geneal for now? To try and clarify
the issue you are seeing.
I can't see the fualt trying to reproduce t
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2676
Version: 1.3-current
Is it possible that there's a header mismatch on your setup?
That is, that the libxft that gets linked at runtime (or compile time)
does not matc
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2678
Version: 1.3.0
Do you have any botes of which versions do work / which version do not
work, to help us pin down the regression?
Also, perhaps you could post a small
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2673
Version: 1.3.0
Or do we just stop fl_input() from beeping?
Why does it beep, anyway?
Link: http://www.fltk.org/str.php?L2673
Version: 1.3.0
___
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2686
Version: 1.3-current
Please bring this discussion over to fltk-general, and bring a minimal
worked example, so we can investigate what's going on. Also post the
examp
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L1986
Version: 1.4-feature
Fix Version: 1.1.10
NOTE: This bug was tied to an apparently similar bug (#2490) on
fltk-1.1.10.
That other bug has recently been closed as
[STR Closed w/o Resolution]
Link: http://www.fltk.org/str.php?L2490
Version: 1.1.10
Fix Version: Will Not Fix
OK - it's been a while now, and no new reports or updates to this STR have
been received.
On the advice of the OP, I am closing this bug.
The advice we have is that this feature is sp
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
Adding to Greg's note above:
- This code is *not* used under the win32 targets, there is a separate
implementation in scander_win32.c for them; howeve
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2639
Version: 1.3-current
I can reproduce it sometimes, using Chris's recipe, but not consistently.
(On WinXP.)
There is something messed up in the resizing though, but I
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2632
Version: 1.3-current
If you refer to the header file Fl_Export.H, you will see that FL_EXPORT is
defined to 3 possible values:
# if defined(FL_DLL)
#ifdef FL_LI
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2634
Version: 1.4-feature
@markcw: I'm temporarily bumping this to 1.4 for now, so we can push ahead
with the 1.3.0 release cycle.
Don't take that the wrong way though -
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2632
Version: 1.3-current
You will need to provide more information:
What host platform?
What compiler toolchain?
What build process?
I can't see what the problem is - m
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2490
Version: 1.1.10
Is this STR still active, or has the problem Gone Away?
It seems that this problem may have been WM or hardware specific? Is that
so?
Do we know if
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2626
Version: 1.3-current
@Kurt - do you have a test sample we can run to see the effect? A simple,
compileable example would be useful.
Manolo can't reproduce it, so an
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2629
Version: 1.3-current
Yup - I had not noticed that, but I just did back to back tests of my app
with fltk-1.1 and fltk-1.3, and the 1.3 build beeps every time I hit a
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2623
Version: 1.3-current
Possibly fixed by r8644, which does appear to resolve the related STR
#2622.
Link: http://www.fltk.org/str.php?L2623
Version: 1.3-current
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2622
Version: 1.3-current
OK - sounds like this might be a working solution then.
Note that I have also pushed a somewhat related fix to a bug that Albrecht
discovered whi
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2622
Version: 1.3-current
Right - I pushed a change at r8643 that I believe fixes this.
Please test on as many variants as possible and let me know.
Link: http://www.fl
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2622
Version: 1.3-current
Albrecht asked:
To Ian: it's your code, and it compiles well with the /broken/ MinGW
wingdi.h, but not with Visual C++ (STR #2623) and the corr
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2622
Version: 1.3-current
Is there any update on this?
I don't have any problem with the win32 builds, but I only ever use MinGW
now, and do not have ready access to eith
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L1899
Version: 1.4-feature
Since this was last updated, Manolo has done a lot of work in this area
(text rendering, GL, OSX, Quartz...) so do we know if this STR is still
e
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2587
Version: 1.3-current
Though most of those added functions are only used if XFT is enabled in the
build (admittedly the default in 1.3) but the build can still be done
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2591
Version: 1.3-current
Whilst playing with the popups demo from the test folder, I notice that, on
popups that have multiple buttons, navigation using the keyboard curs
[STR Closed w/Resolution]
Link: http://www.fltk.org/str.php?L2550
Version: 1.3-current
Fix Version: 1.3-current (r8404)
Believed fixed in 1.3 subversion repository at r8404.
Link: http://www.fltk.org/str.php?L2550
Version: 1.3-current
Fix Version: 1.3-current (r8404)
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Active]
Link: http://www.fltk.org/str.php?L2550
Version: 1.3-current
Link: http://www.fltk.org/str.php?L2550
Version: 1.3-current
___
fltk-bugs mailing list
fltk-b
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2550
Version: 1.3-current
Do we consider this STR resolved now?
If so, I guess we can close this one too...
Link: http://www.fltk.org/str.php?L2550
Version: 1.3-curr
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2550
Version: 1.3-current
@manolo: OK, thanks for that, that seems to have nailed it. (Though more
testing is welcome of course!)
@corvid: The really *safe* way to do
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2550
Version: 1.3-current
Note that many of the Xlib font handling calls will choke like this if
there's no valid drawing context, not just the changes I have made to
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2550
Version: 1.3-current
@manolo - thanks for the feedback. Yes, the unittests demo seems OK and ny
other basic testing also seems fine. Though we need more feedback
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Active]
Link: http://www.fltk.org/str.php?L2550
Version: 1.3-current
Link: http://www.fltk.org/str.php?L2550
Version: 1.3-current
___
fltk-bugs mailing list
fltk-b
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2550
Version: 1.3-current
I have committed a "fix" for this at r8399.
Please test as much as possible as I am not convinced I have this right.
Any feedback or improvemen
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2550
Version: 1.3-current
Looking at this again, albeit briefly, I think we'd be better off
leveraging the logic that's in out utf8Wrap.c (in src/xutf8 in the fltk
tarball
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2550
Version: 1.3-current
Well, sort of - that's a kind of new thing, and I don't know how widely
supported it is. I quote;
"The function Xutf8TextExtents is an extensio
1 - 100 of 228 matches
Mail list logo
