On 03.08.2011 18:22, MacArthur, Ian (SELEX GALILEO, UK) wrote:

>> I'm running it on Win7 here, and thanks to Win7's semi-transparent
>> task bar I can see that the menu is *drawn* behind the task bar in
>> both cases (1.1 and 1.3), so I would say that it is clipped at the
>> screen border.
>>
>> However, srolling starts near the task bar in fltk 1.1, and the
>> highlighted menu item never extends behind the task bar. In 1.3
>> I can see the highlighted menu item *through* the task bar, but
>> scrolling never happens, because (I suspect) we don't get the mouse
>> events any more. And there is only one highlighted menu item
>> visible, i.e. the next menu item below it doesn't get highlighted
>> when moving the mouse further down. (I hope you understand what I
>> mean...)
>
> OK - yes I understand, that makes sense.
> I couldn't tell, on this system, that the menu was behind the task bar
> on fltk-1.1, but thought that it was not.
> In the fltk-1.3 case I managed, on several occasions, to get the menu
> drawn with the text visibly clipped, indicating that it was extending
> behind the task bar...
>
> If we were to make the menu stop at the limit of the "usable" screen
> area, rather than allowing it to draw behind the task bar, do you think
> that would solve this problem?
> It seems to me that it might, and may be easier to do than figuring out
> how to get mouse events (or etc) once the mouse is "in" the taskbar?

Yeah, that's what I was thinking about. Find the responsible menu code
and change the corresponding Fl::screen_xywh() call to Fl::w()... [1]

... but no, that wouldn't work, because secondary screens can have
different dimensions and can have an extended task bar or not. So what
we'd need might be a method that returns each screen's work area
dimensions, and that should then be used in the menu code. Or maybe
similar. I don't know whether we have such a method (I assume not),
and I don't have the time to investigate, sorry.

Albrecht

[1] From what I cited from Manolo's commit message.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to