PolterThanks for the heads up on the build issue, VC11 support not very well tested as it was added in at the last minute...In general I'm trying to improve the build issues and make the whole thing simpler...John

To get the address of the input the parameter, the type of the parameter at registration needs to be XLF_LPOPER rather than XLF_OPER, that way it's not converted into an array before it gets to the function and stays as a reference to the location of the data.John

(copy of my reply to th sam epost to the xlw-users list)It's certainly possible, an number of memory issues were found with the memory code and these have been fixed in the version 5 work, I suggest you upgrade to the latest 5 alpha release which for main usage cases is stable.John

QuoteOriginally posted by: DavidJNYou can make your UDF indistinguishable from a native Excel function. Get a hold of the Excel SDK for details.Really, in cell tooltips with parameter names .....I'd be delighted if you could point out where in the SDK this gets enabled.John

QuoteOriginally posted by: chriswuDoes any way know how to do that with UDF?basically you can't, another one of the annoying ways excel udfs are different from internal functions.John

If you use version 5, get the latest from herehttps://sourceforge.net/projects/xlw/files/xlw/xlw%205.0/There is a new mechanism for automatically building help files.The stuff you need and how to do it should be in the xlw help file.John

QuoteOriginally posted by: FastExcel but I get the feeling that Binary Names are uncharted territory with lurking dragons.Yep, has always seemed like a solution looking for a problem.John

Is this for maintaining the map state within you fast match/lookup functions?I'm going to go with really bad idea, I think working around the scope issues will break any multithreading support as the functions will end up having to be command mode.John

QuoteOriginally posted by: JewBecause all computations (and Excel GUI updating too) are processed in main thread of the process. You should do your computations and Excel GUI updating each in different thread.In other news: the earth is round, beer is good. John

When I tried it, it worked but the sheet wasn't responsive all the time, even with just a few formulas on the sheet it would pause for around a second

<t>QuoteOriginally posted by: GovertThe main issue I know of when implementing RTD (and which Excel-DNA does not have any built-in help for 'in the box') is that you have to follow the COM rules properly. You must either:1. ensure that all your calls to IRTDUpdateEvent.UpdateNotify() are from the ma...

<r>I can't see any overall reason why you couldn't have an all in one xll and rtd server, although setting it all up would be quite fiddly if you're not overly familar with COM. The main issue being registration, the usual methods of registration have 2 issues, requiring an install and the xll depen...

<t>QuoteOriginally posted by: MattFAh I think I see the light ... I can implement something in the xlAutoOpen to get the path to the XLL directory and stick it onto the .chm file thus avoiding the need for the registry.That's possible too but I'd say if your going to have to deploy the help locally ...

<t>QuoteOriginally posted by: MattFUsers can only write to a very limited set of directories, all of which have their usernames in the path, and so cannot be determined in advance.But they can be scripted. How are you getting the users to load the xlls and get them loaded automatically in into excel...

Yes, strictly it's still in testing but there have been lots of fixes since 4.0 though so it probably ought to be the recommended release.John