> I think the problem that we have (still have) in fltk itself is that
> although fltk-1.3 is mostly Quartz based now, there are vestigial bits
> of Quickdraw here and there, so even if SL has a 64-bit Quartz API fltk
> will not build in 64-bit mode...
> Or I could be wrong about that... Matt would
I have a haskell + fltk app. However, the route I took was to write
the gui in c++, and then write an API to talk to it in C (just a set
of 15 or so very short functions), and then FFI that API into haskell.
I also have a C wrapper for Fl::run(), fork off my various haskell
threads and then the m
>and thus creating a hard-to-see deadlock. So you /really/
>have to be careful with threads and locking. I can't remember
>which book it was that opened my eyes to all the insanity
>threading can bring about.. probably one of the Alexandrescu
>or Meyers books
On the cursor side, I guess this means there's no way to get the current cursor?
On Wed, Jun 25, 2008 at 12:50 AM, matthiasm <[EMAIL PROTECTED]> wrote:
>
> On 25.06.2008, at 09:25, Craig D wrote:
>
>>> Is there any interest in general code quality cleanup?
>>
>> This seems like such a religious i
> Yes, everyone who upgraded to 10.5 has this problem.
>
> Apple have removed support for the rez fork hack we've been using up
> 'til now (although to be fair they have been warning that it was
> deprecated for several releases now...)
As an aside, any mac people out there know how to get the .ap
Is there any way to get the current cursor? In my case, I want to
change the focus inside handle(), which might change the cursor and
since the widgets do the "remember the old cursor" hack to avoid
calling cursor() too many times as per the documentation's
recommendation, they won't notice that t
>Hmm, I thought you were talking about overlapping
>/windows/ which is fine, but not overlapping widgets.
>
>You appear to be trying to make overlapping widgets
>both visible at the same time. As far as I know,
>that's a big no-no.
So I actually had a simila
>Kidding aside, I don't find myself defending this kind of design
>(mass overloads of widgets) very often, but in some cases it's
>really the situation calls for, especially real time stuff like
>show control and audio/video production.
[ getting *way* off topic :)
So, my attitude here is probably not like most people's, but:
> UI design...you can make it compact, with submenus, subwindows, search etc
> for "average" users that wouldn't understand all these options at once. Or
> you can make it professional, for the passionate user, that knows what he/she
On Mon, Jun 16, 2008 at 1:26 AM, MacArthur, Ian (SELEX GALILEO, UK)
<[EMAIL PROTECTED]> wrote:
>
>> I am still hunting for a good solution.
>> Lets sum it up again: I must be able to reference every
>> single widget by an ID. I must position and design an UI
>> with, say 1000 widgets
>
> Oh, too ma
> But Fl_Widget doesn't have a value() method. Keeping an array of
> Fl_Valuator* might work, but might get messy because it's value()
> is non-virtual; you'd have to research whether or not the base class
> value() does what you want in all cases. Unfortunately fltk
> doesn't do polymorphism ver
> I want to display a long string without any end of line characters in it, but
> I want the string to be wrapped according to the widget width. It means that
> if there is a word longer that the widget width, the word shall be cut, and
> the rest of it shall be displayed on the new line. If the
I had a problem where some windows could no longer be increased in
size by dragging them. After some investigation, I discovered that
Fl_Window::resize calls size_range with the given width and height.
So after an explicit resize() from my app, it sets size_range to the
size I gave, and sets its m
So I had an odd problem recently: 5 keys on the keyboard mysterious
emitted their qwerty characters (my keyboard is in dvorak). I noticed
that Fl_Input got the correct characters, and noticed that it used
Fl::event_text()[0] instead of Fl::event_key(). Sure enough, for
reasons I haven't tracked d
I've noticed that if the first key I press after the app starts is a
modifier (e.g. shift or control), the keydown for the modifier never
makes it to my handle(). The subsequent keyup makes it, and following
modifiers are fine. If the first key I press is not a modifier,
everything is fine as wel
On Wed, Apr 2, 2008 at 12:05 PM, Greg Ercolano <[EMAIL PROTECTED]> wrote:
> Evan Laforge wrote:
> > As an aside, when I was trying to figure out how FLTK event delivery
> > worked, I found it galling that the documentation had the nerve to
> > describe it as "sim
> I don't think you can use the arrow keys for shortcuts, because they
> tend to get eaten up by other widgets first, e.g. any sort of text
> widget that gets the focus will swallow any arrow keys it sees, for text
> navigation, and at a higher level, arrow keys get eaten by widget
> navigatio
I frequently wind up having a subclass of Fl_Group where I want to
enforce some invariant on the children, for instance that they are all
sorted a certain way, or they all have entries in an auxiliary data
table.
Unfortunately, insert and remove are not virtual, so I have to
remember to call speci
In line with the recent discussion about "modernising" fltk to do
things like transparency, what's the current best way to go about
drawing a translucent rectangle? I.e. something like fl_rect that
takes a rectangle and an rgba color. I have some code that uses
fl_read_image, multiplies each pixe
> > Which platforms have this restriction anyway?
>
> Well, hard to say. I know I have encountered it on win32, although not
Ow, well sounds like I should make main my ui thread just to eliminate
one more variable in the random "things weirdly broken" bughunt.
Thanks for letting me know.
> > >
> > Well, this is what I was hoping to achieve by shipping all gui actions
> > over to the fltk thread to execute.
>
> OK, but not forgetting the key point that, for reliability, the GUI
> thread has to be the main thread, and the non-GUI stuff goes in the
> child threads.
> Some time ago, I had a
> > > > Also, since I am only ever calling FLTK from one thread,
> > I don't think
> > > > I need all the locking and unlocking. Is there a simpler way to
>
> Hmm, from your description it sounds (to me) as if there is more than
> one thread in your process, so you do need to use the lock/u
On Thu, Feb 14, 2008 at 5:01 AM, MacArthur, Ian (SELEX GALILEO, UK)
<[EMAIL PROTECTED]> wrote:
> I'm fairly sure I have not understood your explanation, so what follows
> is likley to be wrong. However, on the basis of what I *think* you
> asked, I don't think this is going to work as you descri
I'm working on an app that drives fltk from a client program. I'd
like to be able to pass events out to the client and also for the
client to be able to run things in fltk. So on the client end I have
a thread which sits in a Fl::wait() loop. When the client wants to do
some fltk stuff, it stick
Hi, I'm new to fltk development, so forgive silly mistakes.
I have an Fl_Tile that is making a "lanes" display. Unfortunately,
when I drag one of the widget edges, it resizes the widgets on both
sides. What I want is for it to resize the widget to the left and
move the ones to the right. Is the
25 matches
Mail list logo
