Hi Albrecht,
Also note that this timer delay compensation works well (i.e. as
designed) on Linux, but probably not on Windows :-( I did some
tests a while back, but lost track of it. I can't say anything
about Mac OS WRT this.
No Windows here, m8 :
just pure Linux amp; microwindows on a 400
Hi Ian,
microwindows is a piece coming from the past.
I have already realized several machines running with AMD Alchemy (MIPS), more
or less same horsepower as the actual one.
It was the usual work of putting together pieces (microwindows + nano-X,
truetype fonts and so on),
but it works.
Hi Greg and Ian,
Use a timer to blink... but things are not always smooth blinking.
Not a big problem, anyway... just would like to know if there is a
clever way to assure a smooth blinking
(usually we are speaking of small objects).
Not really sure this is what was being asked, but
Hi all,
thanks for the observations.
Ian wrote:
I *think* what I'd do is create a group (probably with a FLAT_BOX type) that
contained just the required widgets - I'd populate this at runtime with
widgets as required based on reading the config file.
The redraw would then be sent to the
Hi all,
just to have confirmation of what I am doing.
My app is multithreaded ; the main() loop and some other working threads,
receiving / sending data and doing calculations.
The question: what is the correct way to fire a graphics update from a thread ?
My work (omitted all sanity checks):
Me:
The question: what is the correct way to fire a graphics update from
a thread ?
Albrecht:
Others will probably chime in and tell you more about programming with
threads and FLTK.
Ian:
Ah... That quite possibly means me then...
:-)
Firstly, a caveat: Rendering to the display device
Albrecht wrote:
http://www.fltk.org/doc-1.3/classFl__Widget.html#ac92191cba5d17ae34bfc346d2126c9f2
to damage a particular region (like invalidateRect would do).
It works !
Now forcing a damage to the bargraph parent() passing to it the coordinates to
invalidate.
Removed, for testing, the
Sure; but the Fl::lock() is a mutex, so you must only take it immediately
before you want to modify the widgets, and you release it as soon as possible.
You never hold the lock for any longer than is necessary, and you do nothing
but fltk GUI operations within the lock, so there should be no
Hi all,
forgive me but here is another question, not-so-evident for me.
You have to realize a blinking message, or an object which periodically swaps
two images :
think of an alarm icon.
The alarm is sounding, and the icon keeps alternating red/yellow horn images
until the user pushes the ack
So good speaking with you, boys.
Greg wrote:
If the image is assigned to the bargraph's group, then just telling the
bargraph widget to redraw() will do it.
But if the image is assigned to the parent window, then you'll have to tell
the parent window to redraw.
Be sure to use an
Hi all,
I am trying to create a simple object representing a bargraph.
It is a simple filled rectangle, derived in a Fl_Group ; the draw method simply
draw two rectangles,
one with fill color, the other with background color.
All is ok ; now I want to add a transparent background option.
I
to the parent only the bargraph area ?
Thanks,
regards
Lucio
Messaggio originale
Da: memoryl...@tin.it
Data: 15-mar-2013 10.34
A: fltk@easysw.com
Ogg: Bargraph object with Fl_Group
Hi all,
I am trying to create a simple object representing a bargraph.
It is a simple filled rectangle
Hi Ian,
thanks for your answer.
I am writing to you directly,
Best not - I very seldom reply to off-list posts...
Sorry, will post to the list.
OK: Then you need to composite the bar graph on top of the image.
Fltk does not provide support for transparent widgets (yet) as it is a hard
13 matches
Mail list logo
