1. Win32Lib Bleeding Edge 0.45j
- Posted by David Cuny <dcuny at LANSET.COM>
Jan 11, 2000
-
Last edited Jan 12, 2000
The latest 'bleeding edge' of Win32Lib is available at:
http://www.lanset.com/win32.htm
Some corrections have been made, and some new routines added.
Thanks!
-- David Cuny
2. Re: Win32Lib Bleeding Edge 0.45j
Dave,
Shouldn't that be:
http://www.lanset.com/dcuny/win32.htm
-E.Allen Soard
The latest 'bleeding edge' of Win32Lib is
available at:
http://www.lanset.com/win32.htm
Some corrections have been made, and some new
routines added.
Thanks!
-- David Cuny
---- End Original Message ----
Bookmark the HyperMart Small Business Center. All the tools you need to
succeed!
http://www.hypermart.net/center/
3. Re: Win32Lib Bleeding Edge 0.45j
Allen Soard wrote:
> Shouldn't that be:
> http://www.lanset.com/dcuny/win32.htm
D'oh!
Thanks.
-- David Cuny
4. Re: Win32Lib Bleeding Edge 0.45j
David,
Tooltip hints look nice and work on secondary windows very well.
controls on the TabItem work.
Thanks.
BUT......
from version i to j the combo is not working properly. If you click on an
item in a combo box it does not get brought up into the combo edit field
(gee, I am not sure that is explained very well) unless you click on the
edit field down arrow.
Judith Evans
5. Re: Win32Lib Bleeding Edge 0.45j
Hi, Judith.
> Tooltip hints look nice and work on
> secondary windows very well.
It was a fairly painless fix.
> Controls on the TabItem work.
Thanks. You were the only person to report the bug, so I assume that you are
the only person to have tried them so far.
> from version i to j the combo is not working properly.
The fix for TabItem could have broken other things. Thanks.
-- David Cuny
6. Re: Win32Lib Bleeding Edge 0.45j
Dave:
It is still impossible to run a program from within the IDE. This quit
working
around 45i. What happens is the IDE minimizes to a button on the start
menu,
and the cursor remains an hourglass forever. Clicking on the button does
nothing.
When you do a ctl-alt-del, the task manager shows
Win32Lib IDE - whatever.prj (Not responding)
When you kill that task, there's about a 5 second delay, and suddenly the
program becomes visible, and is running (!?)
Needless to say, this makes the development cycle using the IDE somewhat
difficult.
Regards,
Irv
7. Re: Win32Lib Bleeding Edge 0.45j
Judith Evans wrote:
>
>
> BUT......
> from version i to j the combo is not working properly. If you click on an
> item in a combo box it does not get brought up into the combo edit field
> (gee, I am not sure that is explained very well) unless you click on the
> edit field down arrow.
Not to mention that the combo on the IDE which is supposed to allow
switching between windows doesn't work. That's pretty serious.
Irv
8. Re: Win32Lib Bleeding Edge 0.45j
Hi, Irv.
> It is still impossible to run a program from
> within the IDE. This quit working around 45i.
It seems to be a problem with system_exec (line 1540), but I'm stumped. If
you change the command from system_exec to system, it runs just fine, except
that you get an irritating screen blanking. I've forwarded the question to
Robert.
If all else fails, I can probably get it launched using ShellExecute.
BTW: Robert, under Windows should system( ..., 2 ) really be blanking the
screen? I know it's talking to the console or something, but it would work
much better if it didn't.
Sorry for the inconvenience.
-- David Cuny
9. Re: Win32Lib Bleeding Edge 0.45j
Irv Mullins wrote:
> Not to mention that the combo on the
> IDE which is supposed to allow
> switching between windows doesn't work.
The problem is in WndProc, where Win32Lib is trying to figure out if the
event should be handled by the subclassed routine or not. The logic *used*
to be:
-- if not a window, run subclassed behavior
if window_type[ id ] != Window
and iMsg != WM_COMMAND then
-- run the subclassed behavior
return subclassed(id, hWnd, iMsg, wParam, lParam)
end if
Unfortunately, controls placed in Tab Controls were dead in the water. I had
tried to get this to work:
if window_type[ id ] != Window
and window_class[ id ] != TabControl then
but that caused the controls in the Tab control to respond, but the left the
Tab Control itself invisible. I had finally settled on:
if window_type[ id ] != Window
and iMsg != WM_COMMAND then
but that causes problems with the combo boxes. I'll get it right eventually.
For now, I'm going to go back to the old logic, since it should break the
least amount of code.
As an incentive to keep playing with the bleeding edge releases, the next
version will include Drag and Drop support (by Brian Jackson) and the Color
Dialog (by Wolfgang Fritz). Any errors are of course mine, not their's.
Thanks for all the bug reports!
-- David Cuny
10. Re: Win32Lib Bleeding Edge 0.45j
David Cuny writes:
> BTW: Robert, under Windows should system( ..., 2 )
> really be blanking the screen? I know it's talking to the
> console or something, but it would work much better if
> it didn't.
It would be better if it didn't temporarily
create a console window. It's not something that I do
deliberately. It's part of the WATCOM library routine call.
If I can fix it I will.
Thanks,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
11. Re: Win32Lib Bleeding Edge 0.45j
> > It is still impossible to run a program from
> > within the IDE. This quit working around 45i.
>
> It seems to be a problem with system_exec (line 1540), but I'm stumped. If
> you change the command from system_exec to system, it runs just fine,
except
> that you get an irritating screen blanking. I've forwarded the question to
> Robert.
>
> If all else fails, I can probably get it launched using ShellExecute.
Dave:
Version 45b works fine. I notice the IDE in 45b uses
system_exec( "exw \"" & fName & "\"", 2 )
so I'm not sure that is the problem, or that changing the command to system
is the proper fix.
Regards,
Irv
12. Re: Win32Lib Bleeding Edge 0.45j
Irv Mullins wrote:
> Version 45b works fine. I notice the IDE
> in 45b uses system_exec( "exw \"" & fName & "\"", 2 )
That confirms it's a problem with Win32Lib, but I'm not sure exactly what
the problem is.
When I run a trace, everything is fine until the system_exec() executes.
After that, the trace window goes black. I guess I'll have to roll back
until I find the first version that breaks, and track it from there.
-- David Cuny
13. Re: Win32Lib Bleeding Edge 0.45j
David,
The last version of winlib that did not break system_exe was D. I think that
is also when you added shellExecute. Could that be a connection?
Judith Evans
14. Re: Win32Lib Bleeding Edge 0.45j
David,
I should think before I type.
The last version was indeed D and it did add shellExecute so that could NOT
be the problem. Stupid of me.
Judith
