1. RE: euCom for Tyler
Bernie Ryan wrote:
>
> Bernie Ryan wrote:
> >
> > Tyler Southwick wrote:
> > > I am using w32engin and want to incorperate ActiveX components to it,
> > > but the euCom library developed by Matthew Lewis is for win32lib. Are
> > > there any ways to change euCom to w32engin, or another library out
> > > there? thanks
> >
>
Tyler:
I converted the code over to w32engin.ew but when I run it
I get nothing, not even an error. I guess it's tied to
close to using the win32lib. There are some routines that
are interspered in the code that use functions from the
win32lib which aren't standard window functions that would
have to be written and everytime matt changes his code you
would have to change or rewrite the code. It almost seems
that it would be easier to start from scratch and write
your own version. You will notice that even Matt had to
modify the win32lib to use his code.
The primary reason I wrote the engine was to get away from
using so many files and other users code.I all so wanted
to be easily extendable.
I wanted to get away from non-generic windows code and
wanted to use the "C" type code so I could follow books
written in "C".
I'll let you know if I come up with some kind of solution
but I think you will find that Matt's code will work
if it can be translated to a more generic form.
Bernie
2. RE: euCom for Tyler
> -----Original Message-----
> From: Bernie Ryan [mailto:xotron at localnet.com]
> Tyler:
> I converted the code over to w32engin.ew but when I run it
> I get nothing, not even an error. I guess it's tied to
> close to using the win32lib. There are some routines that
> are interspered in the code that use functions from the
> win32lib which aren't standard window functions that would
> have to be written and everytime matt changes his code you
> would have to change or rewrite the code. It almost seems
> that it would be easier to start from scratch and write
> your own version. You will notice that even Matt had to
> modify the win32lib to use his code.
I'd be interested to see your reworking. A quick scan showed the following
ways the lib ties to win32lib (aside from the demo program):
- sendMessage
- warnErr
- getHandle
- setRect (or moveWindow, or whatever that one's called)
- xShowWindow wrapper
- getDC is in there, but not actually used anymore
- tk_mem.e memory routines
The most difficult would probably be the tk_mem.e code, although that should
actually be compatible with w32engin.ew.
I don't recall anything in the *lib* that needed win32lib to be changed.
For the demo, I changed some local routines to global, and had some bug
fixes that I've been sharing with the list, and which are IIRC now
implemented into the current version. I don't think it's documented, but
try calling com_err_out( 1 ). This will send the error codes to the screen
(default is to NULL). It might identify where some problems are.
Matt Lewis
