1. Win32Lib 0.45p Bleeding Edge
I've posted the 0.45p Bleeding Edge of Win32Lib at:
http://www.lanset.com/dcuny/win32.htm#BleedingEdge
This release fixes some messages being sent to the TabItem. They were
(correctly) trapped in 0.45o because they had null handles.
I've not heard any reports on whether 0.45o fixed the font "corruption"
problem. Can I assume that it's fixed?
Thanks!
-- David Cuny
2. Re: Win32Lib 0.45p Bleeding Edge
- Posted by Robert Pilkington <pilking at BELLATLANTIC.NET>
Feb 08, 2000
-
Last edited Feb 09, 2000
> I've not heard any reports on whether 0.45o fixed the font "corruption"
> problem. Can I assume that it's fixed?
In 0.45l, running a program changed the taskbar's tooltip font to the system
font. In 0.45o, this doesn't appear to happen running the same program that
caused it in 0.45l. (It did this on 3 systems in 45l.. On the third system,
the user told me it affected the tooltips in another program, as well. I
haven't seen any other tooltips affected.) I tested 0.45o on one system so
far.
3. Re: Win32Lib 0.45p Bleeding Edge
David, sorry for not answering quickly... (I was busy reinstalling NT, as
usual after my frequent CrashDebugs)...
Yes, it does like it's fixed... (Further testing needed to be *really*
sure...)
Thanks.
Jesús.
> I've not heard any reports on whether 0.45o fixed the font "corruption"
> problem. Can I assume that it's fixed?
>
4. Re: Win32Lib 0.45p Bleeding Edge
David, sorry for not answering quickly... (I was busy reinstalling NT, as
usual after my frequent CrashDebugs)...
No, it does like it's not yet fixed...
Thanks.
Jesús.
> I've not heard any reports on whether 0.45o fixed the font "corruption"
> problem. Can I assume that it's fixed?
>
5. Re: Win32Lib 0.45p Bleeding Edge
From: David Cuny <dcuny at LANSET.COM>
> I've posted the 0.45p Bleeding Edge of Win32Lib at:
>
> http://www.lanset.com/dcuny/win32.htm#BleedingEdge
Dave:
I notice a difference in the way multiple windows work in 45p as
opposed to earlier versions. Now, when I open multiple windows,
I cannot switch between them via a mouse click as I could before.
The topmost window stays on top, even though the clicked window gets
the focus. Is there something I can change so that the focussed window
will move to the top?
Thanks,
Irv
6. Re: Win32Lib 0.45p Bleeding Edge
Irv Mullins wrote:
> I notice a difference in the way multiple
> windows work in 45p as opposed to
> earlier versions.
Sounds like a bug. I'll try to duplicate it.
Thanks!
-- David Cuny
7. Re: Win32Lib 0.45p Bleeding Edge
One minor change I made to my copy of 45p, you may want to
do this also:
in wPrintf, changed the type of parameter s3 to object, so's I
can print numbers as well as strings.
Irv
8. Re: Win32Lib 0.45p Bleeding Edge
Irv Mullins wrote:
> in wPrintf, changed the type of parameter s3
> to object, so's I can print numbers as well as strings.
Thanks!
-- David Cuny
9. Re: Win32Lib 0.45p Bleeding Edge
Dave:
I have a listbox displaying a list of transactions, and a combo containing
a list of customers.
When I select a different customer from the combo, the first thing the
on_change
event does is eraseItems(ListBox).
Then the routine looks up and adds the newly selected customer's
transactions to the listbox.
Problem is, this process takes a couple of seconds, and the previous data
remains
on view in the listbox until the process is complete.
Is there a way to refresh the listbox immediately after calling
eraseItems(), so it
goes blank, and people aren't confused by seeing some other customer's data?
Thanks
Irv
10. Re: Win32Lib 0.45p Bleeding Edge
- Posted by David Cuny <dcuny at LANSET.COM>
Feb 27, 2000
-
Last edited Feb 28, 2000
Irv Mullins wrote:
> Is there a way to refresh the listbox
> immediately after calling eraseItems(),
> so it goes blank, and people aren't
> confused by seeing some other customer's
> data?
Short answer: You might perhaps call PostMessage instead of SendMessage.
Longer answer: If you send me a snippet of code to play with, I could try to
come up with a solution.
-- David Cuny
