Mike Medved
-
Posts
1,550 -
Joined
-
Last visited
-
Days Won
125
Content Type
Profiles
Forums
Blogs
Gallery
Downloads
Events
Posts posted by Mike Medved
-
-
Yes. Jer will be back in a few days and deal with this.
-
Ok - I open chart. I set its timeframe to be something other than default. I close MT. I reopen MT. That chart still has that non-default timeframe that I selected.
What exactly is the scenario where something goes wrong?
-
We're dealing with the server issues. Hope to have it resolved soon. Blame POODLE and the headlong rush of the industry to switch away from TLS1.0 before the tools for TLS1.2 are ready. And the PCI DSS compliance committee.
-
No, thank you. We wouldn't have known about this otherwise. Blame the hackers that discovered the POODLE attacks on SSL. Now everyone is switching to TLS1.2 and it is a huge pain and it breaks things.
-
1
-
-
Thank you. Will be fixed next release.
To clarify a bit though - did this happen as you were closing or opening charts, or just out of the blue?
-
It was taking DMI Period and using it as the Trail Period. Fixed - will be in next release.
-
Basically, rename it with extension .ZIP and look at it in any ZIP file reader.
-
The last release has help enabled (hit F1). It is context-sensitive, so you will get to a different topic depending on window.
It is not finished, there are still topics not completed, but a lot of it is there. Comments are welcome.
-
At the very start of the chart, you arbitrarily set the direction to up or down. Then, as you go through the algorithm for each subsequent candle, the direction either switches or stays the same.
-
direction length - how many candle are in the current direction period Current Direction - can be up or down do this for each candle: if direction is up if candle high > intra high intra high = candle high increase step by step increment up to step max SAR = SAR + step * (intra high - SAR) if SAR > candle low // switch directions direction = down SAR = intra high step = step increment // initialize step intra low = intra high direction length = 0 else if direction length>=1 and SAR > low of one candle back SAR = low of one candle back else if direction length>=2 and SAR > low of two candles back SAR = low of two candles back else if direction is down if candle low < intra low intra low = candle low increase step by step increment up to step max SAR = SAR - step * (SAR - intra low) if SAR < candle high // switch directions direction = up SAR = intra low step = step increment // initialize step intra high = intra low direction length = 0 else if direction length>=1 and SAR < high of one candle back SAR = high of one candle back else if direction length>=2 and SAR < high of two candles back SAR = high of two candles back direction length = direction length + 1
-
(Almost) none of our implementations will be secret, except ones that are not "public domain", in fact, almost all will be open code as soon as we do the custom indicator support (so that people can look at existing implementations to create their own).
I will give you the algorithm in a bit.
-
Basically, if/when this happens, the best thing to do is: stop quotes, make sure you can repeat the problem by switching frequencies, export both the setup and the data to a file and get us the file, with the instructions on the steps to recreate the problem...
Believe me, when we can recreate the problem, it is a lot easier to fix than just from description.
-
Ok questions:
1. This is for historical charts only, right?
2. What you want, basically, is instead of just having the "start looking 50 bars back" option, have also the "start looking from 4/1/2015" option, right?
-
Rob, as I pointed out in the other post, both Jerry and I pay enormous attention to the GUI and "intuitiveness" of the user experience in general. We discuss/argue about this when we implement features. Jerry and I have about 55 years combined experience in UI design. We have certain principles we lay down as the basis for the UI in MT, such as "maximizing useful screen real estate" and "intuitiveness", and we try to follow them as much as we can when coding. Sometimes we are "forced" to adopt certain conventions and design elements that have gained wide acceptance (such as ribbon menu) in order not to be "outdated", even though we don't fully approve of them.
Please consider reporting the issues in UI that you find objectionable separately. Saying "your UI design sucks" is not helpful, particularly. If you think some feature or window does not flow together with the general design, point it out to us. We're always open to suggestions and we change things quite often when users point out some shortcomings.
-
3
-
-
In Settings - Charts - General, there is "Chart Text Font Size" setting. Try changing it?
Oh, and it is not really glued to the top left corner. You can drag it anywhere you want on the chart.
It also doesn't have to be there permanently. Depending on the Settings - Charts - General's Always Show Trace, it will appear/disappear when you hold the Shift key.
Rob, we pay enormous amount of attention to the GUI and ease of user interfaces... Some features may not be obvious, but I am working on the help file that will include all of them.
-
Gimme a screenshot of TWS style?
-
Was a bug in one of the routines that attempt to detect erroneous data. Fixed in next release.
-
carlisle - I just sit here in the corner and code. MTG is the guy who has some expertise in this, I am sure he can throw in a couple of links.
-
For people other than MTG that are looking at this thread - next release will include "3-touch trendlines" as an indicator. Feel free to try out and comment.
-
1
-
-
MTG, I tried playing with this stuff...
1. I think one of the parameters needs to be "minimum distance between touch points" - in candles/bars, because very often it creates a trendline on points that are very close to each other.
2. It really does not find many (almost none) 3-point lines on any charts I tried, unless you increase the "error" range on the third point quite a bit.
3. I presume if the chart goes through the 2-point line at some point, before it becomes a 3-point line, that kills the 2-point line, right?
4. Can you give me an example historical chart that has a 3-point line like that so I can test my code on that stock's data?
-
Don't worry about pointiness
We're after suggestions however pointed. Anyway - I do like your suggestion. I gotta think about how to implement that efficiently...Question: when you say give a tolerance on 3rd point, does it have to be the middle one of the 3?
-
When you say "2 touches can be drawn between any two points on the chart" you really don't mean that, right? You mean between any two local minima or maxima. Same with the third touch - it has to be the local minimum or maximum.
That's what the "strength" parameter is for the current auto-trendlines - it is the # of candles that define a local minimum or maximum.
-
Yes. Once we allow custom indicators. We need to provide the editor for it, with syntax detection, compile errors etc etc etc. Then deal with the security issues. But we're working on this.
The ticks will be available to you in the custom indicator to compute whatever you want... Still - computing an indicator on every tick (instead of on the candle's values) during a "full recalc" on initialization of the chart will be slow, so I would suggest doing that only on the partial recalcs (that is, as the data comes in).
I will address this in the manual when we release the custom indicators.
-
It's an interesting idea but I would put it on the back burner for now. We are in the middle of an effort to try to finalize MT, create the web site, the help file, the backend etc, and push it out. After that, we will continue normal development.
We're after suggestions however pointed. Anyway - I do like your suggestion. I gotta think about how to implement that efficiently...
Chart custom timeframes
in Bug Reporting - Public
Posted
It should save that setting and it does for me. If you close/reopen the chart (without closing MT) is the setting preserved?