Hi all,
I would like to label a square button with a double line. So I specified in
FLUID the label with "lbl1^Jlbl2" and get in Windows what I wish:
++
| lbl1 |
| lbl2 |
++
but in Linux I get:
++
| lbl1^M |
| lbl2 |
++
Where does the ^M come from ?
Any id
> I would like to label a square button with a double line. So
> I specified in FLUID the label with "lbl1^Jlbl2" and get in
> Windows what I wish:
> ++
> | lbl1 |
> | lbl2 |
> ++
>
> but in Linux I get:
>
> ++
> | lbl1^M |
> | lbl2 |
> ++
>
> Where does
Hello,
I'm working with Windows XP (32Bit), using Visual Studio 2005 Professional.
Now I want to build an Fltk-1.1.10 application (cross-compile) to following
target:
Freescale, ARM1136-MX35 (armv4i), using OS Microsoft Windows CE 6.0
How to?
First I have to build FLTK for WindowsCE.
http://ww
Yes, you are right!
FLUID in Linux shows "lbl1^M^Jlbl2".
Removing the ^M (with the Linux fluid) fixed it and both versions work
nice, now.
(Is it a bug in the Windows FLUID, that it internally replaces a ^J
with ^M^J?)
THNX
Am 23.02.2011 15:59, schrieb MacArthur, Ian (SELEX GALILEO, UK):
>> I
> Yes, you are right!
> FLUID in Linux shows "lbl1^M^Jlbl2".
> Removing the ^M (with the Linux fluid) fixed it and both
> versions work
> nice, now.
> (Is it a bug in the Windows FLUID, that it internally replaces a ^J
> with ^M^J?)
> THNX
Possibly a bug, not sure - the Win32 file system h
> I'm working with Windows XP (32Bit), using Visual Studio 2005
> Professional.
>
> Now I want to build an Fltk-1.1.10 application
> (cross-compile) to following target:
> Freescale, ARM1136-MX35 (armv4i), using OS Microsoft Windows CE 6.0
You may be on your own out there - Mikko is not aroun
I wrote:
> If the widget flag enum says:
>
> INVISIBLE = 1<<1, ///< the widget is not drawn but can
> receive events
>
> then why is visibility required in:
>
> unsigned int takesevents() const {
> return !output() && active_r() && visible_r();
> }
I ask this because the f
corvid wrote:
> I wrote:
>> If the widget flag enum says:
>>
>> INVISIBLE = 1<<1, ///< the widget is not drawn but can
>> receive events
>>
>> then why is visibility required in:
>>
>> unsigned int takesevents() const {
>> return !output() && active_r() && visible_r();
>> }
On 23.02.2011, at 21:22, corvid wrote:
> I wrote:
>> If the widget flag enum says:
>>
>>INVISIBLE = 1<<1, ///< the widget is not drawn but can
>> receive events
>>
>> then why is visibility required in:
>>
>> unsigned int takesevents() const {
>>return !output() && active
Matthias Melcher wrote:
> On 23.02.2011, at 21:22, corvid wrote:
>
>> I wrote:
>>> If the widget flag enum says:
>>>
>>>INVISIBLE = 1<<1, ///< the widget is not drawn but can
>>> receive events
>>>
>>> then why is visibility required in:
>>>
>>> unsigned int takesevents() const {
10 matches
Mail list logo