Jump to content
Medved Trader Forums

Mike Medved

Administrators
  • Content Count

    658
  • Joined

  • Last visited

  • Days Won

    60

Everything posted by Mike Medved

  1. Fixed - go to Dashboard's File menu / Help / Check for Updates
  2. Jason, the problem is the lexical parser we're using does not give the right column for the error sometimes. Correct row though
  3. There are three ways to specify a color. 1. Color.something - like Color.Black, Color.White, Color.Lime etc. - these are absolute colors. 2. SysColor.something - like SysColor.Positive, SysColor.Bid, SysColor.MainIndicator1 - these colors are taken from the current chart's color scheme. 3. the hex format. 0xFF9399FF - the first FF is transparency, just always leave it FF. 93 is the red component, 99 is green, FF is blue. So this color would be a bluish gray. FF is max, so the 0xFF9399FF is a lightish blue. See https://www.color-hex.com/ your 0xFF9399FF would be equivalent to #9399FF there.
  4. Also - in order to scan using several paintbars, you have to combine the several paintbars' code into one scan, and set the scan results or scan result colors differently for the different code's triggers. Only one scan can run on a portfolio at a time.
  5. Scanning is pretty efficient. Past the initial setting up of the scan, as the data comes in, the scan calculation is done only for the last candle. The "problem" with scans is that each symbol has to, initially, recalculate a bit of candle data for itself (how much candle data depends on the indicators in the scan) and keep those candles and the indicator values around while it is running, thus using up some memory. But I know some MT users are running 1500 symbol RT scans with some quite complex code in them and MT seems to handle it ok. Modern computers are pretty amazing in terms of performance. I started programming in the 70s. Computers changed quite a bit during the last 40 years or so. And yes, same code can be used for scans and paintbars. We deliberately made it that way.
  6. The PB's SetColorAndShape sets, unsurprisingly, the color and shape at the particular candle. Where to place that color and shape is not decided at the code level (unless you do SetYValue). At the time you place the paintbar on the chart, in its parameters, you specify where you want that paintbar to appear.
  7. That's the personal service for the complainers. What I meant is it has been fixed and will be pushed out in the next release.
  8. This will work in the beta after the new production that is about to be released.
  9. If you want to overlay and compare two paintbar lines and want to adjust scales, do it in an extra chart (above or below the main one). You can link two indicators to show on the same chart. The linked indicators are usually scaled so that they overlay each other. To do that, if the scales are similar, they do not change, but if they are dissimilar, they are adjusted.
  10. Sorry we missed this post and never answered it. Question: does this happen right away when you run a scan or a long time after the scan starts? Is it some particular scan that causes it? If so, can you export it and send it to us to support email?
  11. TDA is doing a server update for the calculated indexes and it'll be released soon. (Soon = week+).
  12. Well then it should be @BRRU19 in MT as well no? I tried that and it works.
  13. hm. Ok how do you enter it in TWS? I type in BTC, and it gives me no futures option. Same with "Bitcoin"?
  14. Not sure... I cannot easily check since my acct is not enabled for BTC futures right now.
  15. what about @BTCU19 ?
  16. Are you using TDA as the source? I just tried and it is working/updating on the portfolio.
  17. I notified TDA API guys that it is not sending data on $ISSU
  18. You're right, I forgot the public part. And setting it to 999999 would be in PaintbarClearState - but it only affects the candles from the beginning of the chart to the first occurrence of your condition - basically if you don't set it that way, it will assume that the candle right before the beginning of the chart satisfied the condition. As you can see, having C# available to program paintbars/scans is very versatile. Hope the help file clarified things.
  19. There is an option in the ribbon menu to add State to the indicator. That adds a bunch of code, including the CurrentState and a few state-initializing, saving and restoring functions. You put the Boom into the PaintbarState definition: .fctbNone{ color:#000000; } .fctbStyle8{ color:#808080; } .fctbStyle2{ color:#008000; } .fctbStyle5{ color:#0000ff; }/// <summary> /// Holds paintbar state - fill with variables needed to be preserved for next paintbar calc /// </summary> private struct PaintbarState { int Boom; // <--- this is what you add } see https://www.medvedtrader.com/trader/WebHelp/state_keeping.htm I really worked on that help file to make it as comprehensive as possible
  20. Well, the way to do this would be - have a state variable, let's call it Boom (as in "something happened"). Set it to 9999999 or something to begin with. Any time an event happens (like "Outside bar (engulfing)") - set CurrentState.Boom to 0. If the event did NOT happen, do CurrentState.Boom++ This way you can check the CurrentState.Boom to see how far back the event happened.
  21. To tell you the truth, I never liked it It wasn't a true ticker tape (which I believe shows block trades as they happen?). I guess we could make one that would actually do that (show trades as they happen) but I am not sure what criteria to apply (that is, which trades to show). Also, during high volume times it probably would go way too fast?
  22. This is tough to do. Basically, those patterns look great in pictures, but when you look at that stuff in real life... The lines are never exactly parallel, the local minima/maxima are never exactly the same, etc. I will look into it. Candle patterns are a lot easier because they really only work on maximum 5-6 candles. The chart patterns can be quite big - 30-40 candles, right? It would help if there was some word descriptions of those. Like let's say ascending triangle = "local maximum followed by local minimum followed by a local maximum that's approximately the same as first followed by local minimum that's significantly higher than previous one, followed by a move significantly above the maxima" - would that be an accurate description?
  23. When you export, select the "User Settings" checkbox.
×
×
  • Create New...