|
|
On 4/19/24 23:11 Eric Sokolowsky wrote:
Thank you for your response.
Welcome.
I tried what you suggested. Here are my timing results on
your sample program:
~$ time ./tt
FL_API_VERSION = 10304
real 0m7.955s
user 0m0.030s
sys 0m0.013s
It's interesting that most of the time is not accounted to the
running process (user) nor the system (sys). My first guess would be
that the X server or something else is busy and blocks the program,
although the assignment of the text buffer should not cause X server
communication. See below for more questions.
So clearly something is up with my system.
Yes, looks so. You missed to post info about your system, are you
using Unix/Linux (X11) or is it anything else?
Thank you for confirming that this is not expected behavior
from FLTK.
Sure, such extraneous "hanging" is not expected. Did you build FLTK
yourself, or is it from a system package? Can you rebuild FLTK (even
if you're building 1.3.4 again)? If you built FLTK yourself, was it
from an official FLTK release tarball, from anywhere else, and does
it include any patches? Many questions...
Note: one thing that can cause unpredictable effects
is if you mixed FLTK headers from different FLTK versions. Please
make sure that you have only one FLTK version (installed or anywhere
else) on your system, and make sure that you do a full recompile of
FLTK and your application. Note also that FLTK's built-in Makefiles
can't guaranteed to rebuild all files if you update source files.
CMake is much more reliable with checking build dependencies.
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/75a3137a-b393-499e-b96d-a71c95883259%40aljus.de.
[ Direct Link to Message ] | |
|
| |