1 2 ms 3 ms 2 ms popovk@france.com
2 75 ms 83 ms 88 ms ole@spain.com
3 73 ms 79 ms 93 ms jump@bigpond.com
4 73 ms 79 ms 93 ms halifax-le-montreal.com
5 73 ms 79 ms 93 ms shawn@toronto.com (ouch-right on the head)

Trace complete.

;D

Yeah - KIXWIN32 was sort of an experiment to see how KiXtart would work with customizable forms. One of the big problems with anything like this is handling all the "events" that happen in windows - like mouse presses, mouse moves, button clicks - and to top it all off - KiXtart doesn't support ActiveX events - so it makes it even tougher !

So when you say "customizable window" are you thinking along the lines of what was described in the previous post (pre-defined boxes, bitmaps and buttons, etc) ... or were thinking along the lines of how KIXWIN32 works - where you can actually define your own buttons and text boxes...

I personally think it would be more useful to have the pre-defined (but somewhat programmable) window version ... it would certainly make using the window much, much easier if all the windows stuff was managed for you ...

Also, you mentioned that you know VB but did I understand (from your post) that you don't want to learn C ? Like you hinted at, programming OLE in C is definitely a different beast, but there are some nice tools to help you along the way (like MFC and the ActiveX Template Library) ...

But I don't see anything wrong about writing it in VB - nice thing about the VB approach is that you can prototype it real fast - and get working and oget it out there and get feedback on it real quick... then you can adjust and tweak and change it ...

And then you can always look at porting it to C later on, because after all, the script doesn't care what language a COM object is written in - so as long as you don't change the interface - you can write the componenet in just about anything you want ... the interface and the actual window itself are what's important !

Yeah - I'll lend you hand in whatever way I can ... just let me how I can be of service...

And lastly - I'm going to check-out this logonprocess.exe link you gave and see what the scoop is there - did you actually try this yet ?

-Shawn

[This message has been edited by Shawn (edited 15 June 2001).]