Re: Accessing Win API

new topic     » goto parent     » topic index » view thread      » older message » newer message

----- Original Message ----- 
From: "Euler German" <efgerman at myrealbox.com>

> Euman,
> 
> What about ol' Petzold's Programming Windows 95? Do you think it can 
> help?
> 
> -- Euler

I have never read the book but I think David started Win32lib by basing
the code on that book. I think if you ask Derek if he would have done it
this way he'll tell you no and maybe even David dropping the project
may be due to the way he started the library and not wanting to go back
and change everything but, this is just a guess......So, dont base a project on
what you learn from one book!

There are too many lines in Win32lib that make the library redundant, over
sized and slow.."note: I didnt say very slow". I dont know enough yet to
comment on how it shouldve been written but I have ideas.

Anyone who uses Win32lib is stuck in the loop of having code that is poor
in performance, size and bug ridden. Currently there are only a handfull of
people that can write code for Win32lib so your stuck if you have a bug
creap up. Learn to write API from the get-go and you'll be better off in the
long
run. Write your own darn code then you'll feel better about yourself and learn
more, faster...Programs will take many times longer to develop in the beginning
but well worth the time spent researching info either on the net, from books or
the MS-SDK.

I would like to see Win32lib answer what this API means to a program
seterrmode = define_c_func(kernel32,"SetErrorMode",{C_UINT},C_UINT) 
junk = c_func(seterrmode,{SEM_FAILCRITICALERRORS})

hehe just a joke Derek, Matt, Wolf, David..etc

Euman

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu