NaN,

Elaine says she's sorry you're irritated, but is glad to see you have MIDL working...
Posted on 2002-12-05 22:01:35 by Xtreme
Another suggestion,

Im not too fond of the vtable and proto stuff anymore as its alot of overhead and can get you lost quite easily... As such, i've taken to the OLE32 macro that push's and calls by adding an offset to the pInterface to get the correct interface method.

The SAPI.COM i put together is formated for this with simple equates. Would it be also possible to add an options menu selection to spit 'Ernies' version with vtables and protos, or Ancev's version with only equates as i described? And place a basic proto line in a comment following it:



MyCom_QueryInterface equ 00h
MyCom_Addref equ 04h
MyCom_Release equ 08h
MyCom_Method1 equ 0ch ; :DWORD,:DWORD,:WORD
Posted on 2002-12-05 22:08:09 by NaN
Sure, I'm gonna implement all of these suggestions.

Thanks!
Posted on 2002-12-05 22:10:10 by Xtreme
I have to say, The above post was done with no knowledge of you reply.

I need to defend the fact that i would NEVER jump into tech talk without first admirring her, err, Interface first!

... Nice ... I long for the day of 3D T.V.
:alright:
NaN
Posted on 2002-12-05 22:11:53 by NaN
By the way, i downloaded the Script package you suggested, installed and rebooted. But it still did nothing to help the popup window business i was talking about earlier..

Why do you code this in? After every window closes (Create/Properties/Methods/About/Help) it issues a new explorer window and 'trys' to do something with it, but ends up with the standard MS no-server screen. What are you trying to do here? I dug around for souce, but as far as i can tell, this is packaged into your java file (which i didtn see a source for).

:NaN:
Posted on 2002-12-05 22:17:35 by NaN
Another Suggestion:

In your auto-source.asm file:

just before the .code section add this line:
[b] _THIS TEXTEQU <(CTObjData ptr [edx])>[/b]

;-------------------------------------------------------------------------------
.code

CreateCT PROC this_:DWORD
pObjectData this_, edx

; Zero the MyProp property
xor eax, eax
mov [b]_THIS[/b].m_MyProp, eax

xor eax, eax
ret
CreateCT ENDP


Makes things simpler... :alright:
NaN
Posted on 2002-12-05 22:27:43 by NaN
AAAHHHH,

I think I know whats happening. The 'pop-up' aren't my doing.
You might have a Browser Helper Object.

To see my source look in the 'scripts' folder for app.js. The wizard
was done in plain JScript using Notepad.

Could you post a pic of the popup window?
Posted on 2002-12-05 22:29:24 by Xtreme
Heres your PIC...

And by the way, I managed to write and run a compiled com from your wizard. Few bumps to get here, but it paying off! :alright:
Posted on 2002-12-05 22:35:06 by NaN
Yeah, NaN, I see the bumps. :alright:

Norton's antivirus doesn't like me running the scripts.
Posted on 2002-12-06 08:07:46 by drhowarddrfine
Ya, just give it the Autorization its looking for and it will leave you alone...

:NaN:
Posted on 2002-12-06 20:25:25 by NaN
Hey Guys,

I'm making a lot of progress on the 'bumps' front.

NaN, most of your suggestions have been implemented!

drhowarddrfinedrhoward, How is it working out for you? Any suggestions?

TBD, Comments? Suggestions?

Thanks! :alright:
Posted on 2002-12-06 21:30:51 by Xtreme
Error Handling...

I wipped up some macros for Error handling with the Speech stuff.. I dunno if you want to add them to you macro file or no.. its really up to you:


;==============================================================
; E-Z COM Error Handling, by NaN, 2002 Rev 1.1
;==============================================================
IF_COM_ERROR MACRO COM_TXT
LOCAL txtname

.data
txtname db COM_TXT,0
.code
.if eax != 0
mov edx, offset txtname
ret
.endif
ENDM

EXIT_FUNCTION_OK TEXTEQU <xor edx, edx>

FUNCTION_ERROR TEXTEQU < (edx !!= NULL) >


Its made for function based routines, where you call a subfunction full of com stuff, and in the sub function it uses IF_COM_ERROR to return a string pointer describing the error is EDX !=0. As well, the return has the actual COM result in EAX still.

EXIT_FUNCTION is used to simply clear edx before leaving, so that a FALSE error is not triggered.

FUNCTION_ERROR is designed to work with the .if() macro upon return.

.if( FUNCTION_ERROR )

.else

.endif.


Anywho.. feel free to expand on it as well if you think its a good idea!
:alright:
NaN
Posted on 2002-12-06 21:42:58 by NaN
Xtreme, hows the wizard going?

You've been silent for the last 3 days or so??

:NaN:
Posted on 2002-12-09 23:35:25 by NaN
Posted on 2002-12-10 08:54:01 by Xtreme
Hey,

I'm still here! :grin:

While I'm fixing the bugs I might as well fix them all.......
Posted on 2002-12-13 10:40:28 by Xtreme
Sorry, guys.

I know you want the Wizard finished ASAP, but I just cannot get events to work correctly.

Its strange, but the methods, properties, and events work intermittently. :eek: :eek: :eek:

NaN, all of your suggestions have been implemented completely.

Any Ideas?
Posted on 2002-12-17 15:37:06 by Xtreme
Thanx... i dont really know what your "event" problem is, without seing it ;)

Can you provide something for us to perhaps help out with? Perhaps your test-bench source as well, to see how your getting a problem?

Cant say i will be of any help, but you never know :tongue:

Best of luck.
:alright:
NaN
Posted on 2002-12-17 16:47:26 by NaN
Xtreme,

how is this project going?

where can i download the latest version?

Thanks

I just need something like this.
Posted on 2003-01-30 14:55:49 by chrislee8