Hi all.
Been playing around with automating Excel from Dolphin today, and I pretty much managed to get working everything I wanted. Thank you all for lots of wonderful examples related to using Excel from Dolphin, they've been a great help! Now, I have a question about one of the types of errors that gets reported in the Dolphin System Transcript while using Dolphin's ActiveX wizard to generate all the needed wrapper classes for different Excel's COM object types. I have no idea why these errors get reported, whether they really do point to something that went astray during the generation process or if they're perhaps just results of a bug in the wizard. Here are some examples of these error messages: Error: ExcelRange>>address at line 7: undeclared 'rowAbsolute' Error: ExcelRange>>addressLocal at line 7: undeclared 'rowAbsolute' Error: ExcelRange>>characters at line 7: undeclared 'start' Error: ExcelRange>>_default at line 7: undeclared 'rowIndex' Error: ExcelRectangles>>characters at line 7: undeclared 'start' Error: ExcelRoutingSlip>>recipients at line 5: undeclared 'index' Error: ExcelTextBox>>characters at line 7: undeclared 'start' Error: ExcelTextBoxes>>characters at line 7: undeclared 'start' I've checked the sources for these methods and they all seem perfectly correct. In every instance the wizard seems to complain on access to the object passed to the method as its first parameter. Also the given method names are not correct - only the first selector in the method name is stated in the error message, and without the terminating colon sign at that. I guess they could be referring to something else, but what? Anyone have any ideas? Thanks, Jurko |
"Jurko Gospodnetiæ" <[hidden email]> wrote in message
news:bspj9i$7eg$[hidden email]... > Hi all. > > Been playing around with automating Excel from Dolphin today, and ... > ... I have a question about one of the types of errors that gets reported > in the > Dolphin System Transcript while using Dolphin's ActiveX wizard to generate > all the > needed wrapper classes for different Excel's COM object types. I have no > idea > why these errors get reported, whether they really do point to something > that went > astray during the generation process or if they're perhaps just results of > bug in the > wizard. > > Here are some examples of these error messages: > > Error: ExcelRange>>address at line 7: undeclared 'rowAbsolute' >....etc... Jurko these would appear to be due to a bug in the analyser. Can you tell me which version of Dolphin you are using, and which version of the Excel type library? Regards Blair |
Hi Blair.
> Jurko these would appear to be due to a bug in the analyser. Can you tell me > which version of Dolphin you are using, and which version of the Excel type > library? Dolphin Smalltalk, version 5.1.3. Microsoft Excel 10.0 Object Library, version 1.4 HTH, Jurko |
Hi Blair.
> > Jurko these would appear to be due to a bug in the analyser. Can you tell > me > > which version of Dolphin you are using, and which version of the Excel > type > > library? Any new developments regarding this bug? Best regards, Jurko |
Jurko,
> Any new developments regarding this bug? Depending on what you doing, you don't need the analyzer. See some IDispatch examples and my WordAutomation package. In fact, for such work, I recommend _not_ using the analyzer. If the Microsoft IDL were better, the output of the analyzer (a truly amazing tool!!!) would be better. As it is, the output is big, and not all that helpful. Also, see "VBA for Dummies", especially the extra documentation on the CD. Have a good one, Bill -- Wilhelm K. Schwab, Ph.D. [hidden email] |
In reply to this post by Jurko Gospodnetic
"Jurko Gospodnetiæ" <[hidden email]> wrote in message
news:bu8baj$2rp$[hidden email]... > Hi Blair. > > > > Jurko these would appear to be due to a bug in the analyser. Can you > tell > > me > > > which version of Dolphin you are using, and which version of the Excel > > type > > > library? > > Any new developments regarding this bug? Sorry Jurko, I'd drafted a reply but forgot to send it. Here it is: Thanks. The issue is with the generation of the wrapper method which defaults all optional arguments in the specific case of the property get methods of dispinterfaces. This will be fixed in PL4, and in the interim I have attached a hotfix below. Regards Blair ----------------- "#1478"! !TKindDispatchAnalyzer methodsFor! printPropGet: aFUNCDESC wrapping: anAXMethodName on: aPuttableStream defaultOptionals: aBoolean "Private - Generate the main body of a high-level accessor for the prop-get method described by the <FUNCDESC>, method. Answer nil if no method is to be emitted." ^aBoolean ifTrue: [self printDefaultMethodBody: aFUNCDESC wrapping: anAXMethodName on: aPuttableStream] ifFalse: [self printRawPropGetBody: aFUNCDESC name: anAXMethodName on: aPuttableStream]! ! !TKindDispatchAnalyzer categoriesFor: #printPropGet:wrapping:on:defaultOptionals:!development!private! ! |
Free forum by Nabble | Edit this page |