开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
  1. Twsapi
  2. Messages
Single Messages Topics Expanded Polls

Re: ActiveX in API version 9.72 and later

 

开云体育

Well, I’m spending time on it because the problem has interested me, not specifically for you, though if it ends up solving the problem for you so much the better.

?

It bugs me because it should ‘just work’. I suspect the problem is of IB’s making, and nothing to do with Delphi per se. A .Net component that exports a COM interface should work seamlessly in any COM-compliant environment, and Delphi is certainly one such.

?

I actually owned a copy of Delphi Enterprise back in the Borland days, but never got round to making use of it. I much prefer the Pascal language style to the C-derived languages. I had the misfortune to have to write a few thousand lines of C code back in 1989/1990, and I ended up feeling that C was the most awful write-only language you could imagine – except perhaps for APL! This was largely a result of having been spoilt by exposure to ICL’s Algol 68-derived languages S3 and SCL, which made C seem primitive. I’m afraid I don’t worship at the altar of Saints Kernighan and Ritchie, which is perhaps also why I’m averse to Unix and all its progeny.

?

?

From: [email protected] [mailto:[email protected]] On Behalf Of rwk
Sent: 07 October 2017 19:44
To: [email protected]
Subject: Re: [TWS API] ActiveX in API version 9.72 and later

?

On Sat, Oct 7, 2017 at 10:44 am, Richard L King wrote:

In the meantime, is there any particular reason that you need to use more recent versions of the API? 9.69 was a standard .ocx component and I’ve no doubt that worked with Delphi. If you don’t actually need any of the features added to the API since then, why not just revert to it? At least you wouldn’t have to rewrite in another language. Bear in mind that the APIs don’t go ‘stale’: earlier this year, just for fun, I installed the first API version I used back in 2003 (version 7.30) and it still works fine, though of course there are vast swathes of current functionality missing from it.

My motivation for this was essentially the possibility of a forced upgrade of which there have been few, thankfully.? I am running API 9.64 and it does everything I need.? I recently upgraded the TWS and inadvertently broke my app, but that was easily fixed.? I think it was the latter that motivated me to "not get too far behind IB".? I like Delphi/Pascal a lot, but it's not very popular in the USA, and it has gotten quite expensive to buy.

I've been a programmer since 1971, but I am entirely self-taught on the PC since 1996.? When I started programming with the TWSAPI in 2003, I decided to use Ross Hemingway's IABSocket component mostly because of the support he provided.? The component is still available and up to date, but I later switched to the ActiveX because I was concerned that if Mr Hemingway ever decided to discontinue his product, that would leave me with no upgrade path.? I depend on trading for paying expenses, not a condition I recommend, and I am always trying to anticipate what could go wrong.

I suspect using the ActiveX in API 9.72 and later might require an intermediate step to support non-Microsoft technologies.? I don't consider that a good use of my limited resources and ability, so please don't spend time on it for me.? I'm ready to move on to other challenges.
[rwk]

Join [email protected] to automatically receive all group messages.