Installed Kase Statware and now I can't compile any of my code

[cunparis]

I hate that. Has happened to me before as well.

Mike

It gets worse. I spent hours just attempting to code up her strategy from her book only to discover that the indicators do not work properly in a multi-timeframe strategy! I use 3 timeframes like she suggests but the value of the indicators are the same for all my timeframes!!!!!

I'm afraid I've wasted all my time and nothing to show for it.

[Elliott Wave]

I haven't contacted them yet because this was over the weekend.

I get the impression that it may have been on purpose. I do not think they were designed to be used in a strategy because there are visual indicators drawn on the graph that are not available via the indicator properties. this makes them less useful than I originally thought.

Also the strategy in her book seems quite complicated to code in a strategy. It uses multiple timeframes and divergences.

This doesn't make sense to me. Dev stops, permission function, KCD, PeakOsc are all very usable as part of any strategy. On the other hand, considering how well the indicators are coded for NT, this just being a sloppy coding error seems a bit unlikely.

By using the work around I posted I've been able to use them in strategies, after everything compiles correctly, just change the file back to its proper name and hopefully it will work...

[cunparis]

This doesn't make sense to me. Dev stops, permission function, KCD, PeakOsc are all very usable as part of any strategy. On the other hand, considering how well the indicators are coded for NT, this just being a sloppy coding error seems a bit unlikely.

By using the work around I posted I've been able to use them in strategies, after everything compiles correctly, just change the file back to its proper name and hopefully it will work...

The entire Kase methodology is based on multiple timeframes, divergences and peakouts. The divergences are drawn on the chart but are not available via indicators. That's ok I can code it up but it shows a lack of forethought. The easy entry indicators draw on the chart but the signals aren't available through the indicators either so I can't use them (not sure they're useful but I would have liked to have tried some testing before investigating time in them). Same for the candlesticks.

But the worse is that the indicators do not work with multi-timeframe strategies, which is the most important part of her strategies! Here is an example:

KaseOdds1a 2007-08-31 15:30: ES 60 Min
KaseOdds1a 2007-08-31 15:30: kcd = 2.99163055419922

KaseOdds1a 2007-08-31 15:30: ES 15 Min
KaseOdds1a 2007-08-31 15:30: kcd = 2.99163055419922

KaseOdds1a 2007-08-31 15:30: ES 5 Min
KaseOdds1a 2007-08-31 15:30: kcd = 2.99163055419922

You can see that kase kcd is the same on all timeframes.

So yes you can use the indicators for other strategies but not hers. As I said, it's clear that these indicators were not designed to be used in an automated strategy. Or maybe it's so that one can't backtest the strategies?

Sorry if I see harsh but after investing several days on these only to find out they don't work, I'm a bit put out.

[cunparis]

This doesn't make sense to me. Dev stops, permission function, KCD, PeakOsc are all very usable as part of any strategy.

I'm not sure I get the devstops. From what I see they're often on the wrong side so I set the ma's to be 5 & 13 which correspond to the ones she uses in her strategy for the timing chart signal. If I use the default then when there is a 5/13 cross the stops are on the wrong side and I got stopped out. If I put 5/13 then basically they never get hit and it's the same as using a 5/13 crossover for an exit. I figure i must be missing something here.