Mike Medved
-
Posts
1,543 -
Joined
-
Last visited
-
Days Won
124
Content Type
Profiles
Forums
Blogs
Gallery
Downloads
Events
Posts posted by Mike Medved
-
-
make sure the extended hours on your scan is set to "never" if you want the 1st candle to be the first session candle.
-
int DayNum = -1; double FirstMinVol = 0; public void MainCalculation() { if (TradingDay.DayNumber!=DayNum) { DayNum = TradingDay.DayNumber; FirstMinVol = BarVolume; } SetScanResult(FirstMinVol*10); } -
That would work. If you encounter serious slowdowns, the Count functions could be replaced with manually counting using two StateFIFOQueues. Instead of looping (which is what Count does).
-
Do you mean period or frequency (candle size)?
I am not really sure what you're trying to do. If you want your API-using program to do different things depending on what chart window is currently "active" then the APIKeyPressUpdate is what you want.
-
Define "long-term uptrend (not necessarily monotonic)" algorithmically. Maybe "in the last 30 candles, at least in 20 of them the EMA went up"?
Same with "short-term downtrend" for candles? - "In the last 6 candles, at least 5 were up, and the last one was up"?
You will find that once you define these things for yourself, writing the scan becomes a lot simpler. -
1. That 'Buy' and 'Sell' variables - put them in Variable section. Makes it easier
Not sure about your +33 / -33 third leg but I retained it here. Something like this?
-
CapOrderType is the order type of the Capsule over which the mouse is hovering. Since there is no capsule, don't use it.
I would suggest using insteadPriceAtMouse<=Price?'Buy':'Sell' for the main order and
PriceAtMouse<=Price?'Sell':'Buy' for the legs?
Also - I am not sure how you decided on your limit and stop prices both in main and in legs. That doesn't look like it works both for sells (if mouse is on left side of DOM) and buys (if mouse is on right). Are you sure about those? -
You can definitely just have a separate connection - the internal server can handle thousands of connections.
-
Jason, MT's Websocket API is mostly asynchronous.
That means that you send a command and don't wait for immediate response to the command. The response will just come when it comes (usually pretty fast but still). You can match the command to the response by sending a unique reqID in the command and matching it to the reqID in the response.The part that processes responses and decides where to direct it does not really has to be multithreaded - it should be very fast. But once you receive and parse the response you can direct it to a separate thread or queue if you like. Although I would wonder if that's overkill. Usually such processing is fast enough and the events that happen are (comparatively) rare enough (that is, not 100s a second) that multithreading may not be needed.
-
2023-06-23T13:30:00.000 - that's UTC time. Currently 4 hours difference from Eastern. So that would be 9:30 Eastern.
-
3 hours ago, Hans said:
Mike - in your last example, is it not necessary to specify Quantity in each of the Sell bracket legs?No - it would be copied from the main leg of the order. In fact, most brokers I think don't allow quantities in sub-legs that are different from main.
-
Actually, Niko, I should amend my previous answer.
This waiting for an order to execute cannot be done on MT side. But it can be done on the broker side, if your broker supports it. So if your broker supports OTOCA orders, here is a hotkey
-
The limiting thing here is, the hotkey just executes, section by section. It cannot wait for one order to complete before continuing. There is no mechanism to do that.
-
will be done in next beta.
-
If instead of "Buy limit x% of account" you'd accept "Buy market x% of account" and then assume that it was bought at current Ask (for the "entry" part of the subsequent orders) - yes you can.
Or - if you split it in two. One hotkey would do the "Buy limit x% of account". And the other (that you would execute once you see the buy go through) would set up the other two OCO orders. -
You cannot do that for several reasons.
1. Limit order is definitely not guaranteed to fill in 5 seconds (which is the delay you set)...
and
2. Even if it did, the variables that are used in the hotkey are set at the beginning of the whole hotkey, and are not recalculated at the beginning of each section. So if you have no position at the start of the hotkey, the PosAbs will be 0 even if the first section executes an order and a position appears.
What you would have to do is calculate the quantity and make it a variable in the variable section at the very start of the hotkey. Then use that variable in the subsequent sections. Same for the Paid price. And still have to take the (1) fact above into account. -
ok I see why. If you click on that checkbox twice (remove it then re-add it) in that row, it will correct. The switching from buy/sell and call/put was screwed up. Will fix.
-
Click on Drag-Scroll in the Draw selection in the chart.
-
Hans, place a "Paintbar" indicator on the chart. Select the paintbar you created inside that indicator. There are also options on how to apply the paintbar, visually, to the chart. For your purpose, select the "Color Candles" method.
-
What color would you want a doji candle to be?
Let's say you want it always to be the positive color.
Then you configure a paintbar that says "If Close>=Open then Positive Color else Negative Color."
Put that on the chart, then make it color candles. -
Yeah, that would be a separate option in Compare Symbol. Will see about it.
-
Shift - toggles between trace and no trace.
Ctrl-Shift - toggles between freestyle trace and snap-to-candles.
-
Yes. Hotkey has a PriceAtMouse variable you can use.
-
Well. The options in the Compare Symbol is -
Anchor and Fit - which shows the %Fit Scale to Overlap - which shows the Compare symbol fitted into the chart, with the Min/Max fitting.
Share Scale no Fit - which makes the scale big enough to fit both.
MacDHistogram Values not consistent on Chart vs. Paintbar
in Bug Reporting - Public
Posted
The two should match. The easiest way to check is to set Scan value to the histogram's value, and compare the value you see on the portfolio to the one you see on the chart.
The problem you're seeing may be a mismatch either in the candle size or in the extended hours between the chart and the scan. Those should be exactly same in order to match.