1. [Win32Lib] Control Heights Inconsistency

I always thought it was Judith's IDE causing this problem, but now I think
it's with Win32Lib...

Notice how both controls (rich edit and list) are created as height 170, but
only one renders that way.

Derek, can you explain this?

--  code generated by Win32Lib IDE v0.18.1

include Win32lib.ew
without warning

----------------------------------------------------------------------------
----
--  Window Window1
constant Window1 = createEx( Window, "Window1", 0, Default, Default, 272,
257, 0, 0 )
constant EditText2 = createEx( EditText, "30,30", Window1, 30, 30, 40, 20,
0, 0 )
constant EditText3 = createEx( EditText, "200,200", Window1, 200, 200, 48,
20, 0, 0 )
constant RichEdit5 = createEx( RichEdit, "Height: 170", Window1, 73, 30, 50,
170, or_all({ES_NOHIDESEL}), 0 )
constant List6 = createEx( List, "Height:170", Window1, 150, 30, 50, 170, 0,
0 )
---------------------------------------------------------

WinMain( Window1,Normal )

new topic     » topic index » view message » categorize

2. Re: [Win32Lib] Control Heights Inconsistency

Unless you're using LBS_NOINTEGRALHEIGHT as one of it's parameters, any list
will auto-size to the closest number of lines that fit what-ever font's
bein' used...

> I always thought it was Judith's IDE causing this problem, but now I think
> it's with Win32Lib...
> Notice how both controls (rich edit and list) are created as height 170,
but
> only one renders that way.

new topic     » goto parent     » topic index » view message » categorize

3. Re: [Win32Lib] Control Heights Inconsistency

> > I always thought it was Judith's IDE causing this problem, but now I
think
> > it's with Win32Lib...
> > Notice how both controls (rich edit and list) are created as height 170,
> > but only one renders that way.

> Unless you're using LBS_NOINTEGRALHEIGHT as one of its parameters, any
list
> will auto-size to the closest number of lines that fit what-ever font's
> bein' used...

Well that's good to know... Although if I specify a height of 170, I want a
height of 170... no more no less.

new topic     » goto parent     » topic index » view message » categorize

4. Re: [Win32Lib] Control Heights Inconsistency

if you do this:

    LB = create( List, "", Parent, 10, 10, 100, 100, LBS_NOINTEGRALHEIGHT )

then your list box will stick to whatever height you give it, if you want
170, so be it.
when a list box uses "integral height" it rounds down the height to the
maximum number of elements that may be show in your given height. using no
"integral height" will allow the excess to flow over, showing half of an
item or white space.

~Greg


----- Original Message -----
From: "C. K. Lester" <euphoric at cklester.com>
To: "EUforum" <EUforum at topica.com>
Sent: Friday, October 10, 2003 4:36 PM
Subject: Re: [Win32Lib] Control Heights Inconsistency


>
>
> > > I always thought it was Judith's IDE causing this problem, but now I
> think
> > > it's with Win32Lib...
> > > Notice how both controls (rich edit and list) are created as height
170,
> > > but only one renders that way.
>
> > Unless you're using LBS_NOINTEGRALHEIGHT as one of its parameters, any
> list
> > will auto-size to the closest number of lines that fit what-ever font's
> > bein' used...
>
> Well that's good to know... Although if I specify a height of 170, I want
a
> height of 170... no more no less.
>
> --^----------------------------------------------------------------
> This email was sent to: g.haberek at comcast.net
>
>
> TOPICA - Start your own email discussion group. FREE!
>
>

new topic     » goto parent     » topic index » view message » categorize

5. Re: [Win32Lib] Control Heights Inconsistency

Okay, then... Judith! Can you make it the default behavior, that list items
are created with LBS_NOINTEGRALHEIGHT? :)

thanks everybody for your help!

> if you do this:
>
>     LB = create( List, "", Parent, 10, 10, 100, 100,
LBS_NOINTEGRALHEIGHT )
>
> then your list box will stick to whatever height you give it, if you want
> 170, so be it.

new topic     » goto parent     » topic index » view message » categorize

6. Re: [Win32Lib] Control Heights Inconsistency

I just put it in under Styles > Other Flags..

Perhaps Judith could insert a listing for "Integral Height" which could be
unchecked, so when it was selected, the LBS_NOINTEGRALHEIGHT flag would be
removed.

----- Original Message -----
From: "C. K. Lester" <euphoric at cklester.com>
To: "EUforum" <EUforum at topica.com>
Subject: Re: [Win32Lib] Control Heights Inconsistency


>
>
> Okay, then... Judith! Can you make it the default behavior, that list
items
> are created with LBS_NOINTEGRALHEIGHT? :)
>
> thanks everybody for your help!
>
> > if you do this:
> >
> >     LB = create( List, "", Parent, 10, 10, 100, 100,
> LBS_NOINTEGRALHEIGHT )
> >
> > then your list box will stick to whatever height you give it, if you
want
> > 170, so be it.
>
>
>
> TOPICA - Start your own email discussion group. FREE!
>
>

new topic     » goto parent     » topic index » view message » categorize

7. Re: [Win32Lib] Control Heights Inconsistency

Greg Haberek wrote:

>
>
>I just put it in under Styles > Other Flags..
>
>Perhaps Judith could insert a listing for "Integral Height" which could be
>unchecked, so when it was selected, the LBS_NOINTEGRALHEIGHT flag would be
>removed.
>
Yep, that's where I put it. And she's already got checkable "Read Only" 
and "H Scroll." I wonder if I should ask what those are for...? :)

new topic     » goto parent     » topic index » view message » categorize

8. Re: [Win32Lib] Control Heights Inconsistency

I will add LBS_NOINTEGRALHEIGHT  flag to IDE's Properties. However, so as
not to break existing code, the default will be to create the control as it
presently does. If this flag also applies to ListView I will add to ListView
Explorer.

Read Only and H Scroll are for edit controls. Rich Edit will wrap long lines
without H Scroll flag. What you want depends upon the use of the Rich Edit
control. Some times you may not want it to wrap. Read Only prevents user
keying data into the control.

In IDE.htm if a Property is specific to a particular set of controls, I've
tried to remember to add that information in the 'Using Properties' table.

HTH,
--judith

>>Perhaps Judith could insert a listing for "Integral Height" which could be
>>unchecked, so when it was selected, the >>LBS_NOINTEGRALHEIGHT flag would
be removed.
>Yep, that's where I put it. And she's already got checkable "Read Only"
>and "H Scroll." I wonder if I should ask what those are for...? :)

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu