Posts made by MrDaisyBates

Hahahaha. And to be fair, @l-andorrà , I did take your advice and email him first! haha. So. You might have been correct. Don't be too hard on yourself. Appreciate you, bud.

And to @fxDreema , that's really great to hear and I'm glad it's already in the back of your mind. I'm patient. I just wanted it out there.

Eliminating the scroll bars and with zoom might be an interesting combo. I assume kind of like an infinite canvas like you see on many other, modern applications (like Obsidian's Canvas, for example).

If you're in the process of doing all of that anyways (and you're already probably thinking of this, but I'd like to say it for the record), one night, I was on my phone and looking at a forum post about something, and there was an example project linked with a custom code block...and there was no gesture for me to access and see its contents! I know phone isn't optimal, but it'd be really nice if I could at least like long press and then select the block's contents window via the menu that comes up. There's likely some other mobile/tablet specific pain points, as well. Again, I know it's not optimal, but if you're already gutting and redoing everything anyways, it's probably worth having in the back of your mind.

That's my two cents regardless.

Really appreciate what your'e doing here regardless. Just wanted to voice some thoughts. I've said what I thought and consider this closed on my end. Appreciate your consideration in these matters.

Thanks, @l-andorrà ! I guess he doesn't check here?

Did he tell you that or something? I'm kind of of the mind of letting him speak for himself. Hahaha. We'll just have to see.

I guess you're suggesting that I @fxDreema ?

There's not a dedicated area for feature requests, so, I figured this was the best area for it.

I really appreciate the fact that FxDreema has such meticulous historical tracking. It's a needed feature.

I'd like to request an optimization for it.

In the past, I've often made a bunch of different versions of the same project, mainly because I want to preserve certain states.

Instead, I really like the idea of a project staying a project and having some version control. My thinking is like git would, for example. As in, it's still tracking all the changes, as per usual, but with the gained ability to make a "commit."

Basically a commit would be a saved version within the project.

So, once loading the project, we could also toggle different commits (to reactivate old states and whatnot). Call it what you will. I just like the idea of being able to have a project for one trade idea, but being able to toggle between different save states (and then resave them before switching to another, if we so wish to).

I think the benefits are self evident, but in making a request, I feel obligated to demonstrate why it would be useful.

I'm designing something as a prototype right now. I will not use it live. It's just a proof of concept. I'd like to keep it forever, and then start a Version 1, Version 1.1, Version 1.2, Version 2.0, etc.

It's all one project technically...just different points in history or time.

I also feel like the QoL on this is quite nice and I (assume) it wouldn't be THAT big of a task since it seems you already have the most essential building blocks in place.

Anyways. That's all. Thanks. Feel free to close this if this is something you're not interested in doing.

@l-andorrà Thanks for the reply, bud. Sorry for not being clear enough.

I'm thinking every 1m candle (or any timeframe for that matter) with a server time of XX:05, I want it to give me a "true" output. And all others, a false.

So, I would like a condition, that when I run through a loop (increasing candle_id), then every time I hit an old candle with that server time, I want it identified.

@l-andorrà Sorry to tag you. Is this something you're capable of answering? I know time is a quite tricky thing in Dreema. I'd like to refrain from dragging Roar in if I can avoid it. I feel bad for how he's basically the only person who can answer almost everything (that regularly answers anyways ahahaha).

Hello again, lovely people!

I've attempted to create a loop that goes through old candles and then marks them if they meet certain time criteria.

Specifically, if the loop hits a candle with six minutes (all hours), then draw something on the candle before.

So, what I need is a "condition" that will detect "true" when the time on the loaded candle has a set amount of minutes, but doesn't discriminate by hour or anything else.

I've tried a few different things, but this is the main one I feel is closest?

When I drop it on a chart, it's not ever making it to the draw commands I have. I put a custom MQL block with a print command down there and it's never printing anything (this is only able to be done after detecting a valid candle, and it never happens). So, I'm assuming that it's never flagging valid candles.

Thanks in advance for the help.

@roar Thank you for your help and hospitality, Roar!

I feel I'm still learning and fumbling, but managing with all of the above. I'm sorry for the delay in replying. I just didn't want to rush back in haste. But I still wanted to thank you. So. I appreciate you! I'll keep at it and see if I can keep fairing. Haha.

Take care until we cross paths again!

Upon more research, it seems stack overflow problems are caused when an infinite recursive loop is in place. So, I will continue to try to solve this myself since it's not array related (I assume it's not?). I can't say for certain that the array stuff is "solved" until I button this up, though, since I can't test my array stuff ahaha.

I looked up what a stack overflow is. Apparently is a memory issue?

I want to be up front, in case it matters, that I'm running MT5 through a windows emulator on Linux basically. I'm not sure if this stack overflow is some limit that MT5 has or a limit that the way my MT5 is installed is (or neither). I just want the information out there if it's relevant. I can and will look into this, also. When it comes to running these EAs (eventually one day), I'll do it on a VPS from a windows machine, but I don't use windows as my daily driver, for whatever it's worth. Idk if it's at all relevant here.

Edit: I don't believe this is an issue. I loaded up the task manager for the emulator that my MT5 is running on and we never used even more than 10% of its resources.

Edit again: I double confirmed the Linux isn't an issue by popping over to my windows virtual machine and ran into the same stack overflow error when I ran it on MT5 there.

@roar This "Print()" tip is super handy! Thanks for sharing it.

I noticed I got a "stack overflow" (whatever that means ahaha. Sounds bad). I'm going to research what that means, but I imagine the problem could lie there?

@roar Neat! I'll try messing with that now. Don't kill yourself over it. I'll be working on it again all day tomorrow, too. Until I get it. I didn't know that Print function, so I'll try that and it'll give me a much much better idea what's going on. I really appreciate it!

I'm looking at your first condition. You might not want it set to "crosses above" and instead just above/below. At least the way I have it structured anyways. Unless you only want it to happen on that exact candle. "Crosses above" as you know is more of a single signal. If you want that, then you do you. Just a heads up.

You can obviously do it as you please, but I'm hoping it illustrates what I mean by the bool logic to make it happen. Basically, if condition 1 isn't met, you can see your bool is set to false. If it is true, we move on to the second condition. And there, if the condition is not true, then we set the bool to false still. However, if the second condition is true, the first one must have also been true to even get to that point.

Then for your execution, you can see all we simply need to do is check if the bool is set to true or false. And if it's set to true, then we check for the signal condition.

https://fxdreema.com/shared/yL3iwJy9e

This might give you an idea.

@Maysam Okay. So. To make sure I'm following.

You want condition 3 to be your signal. The other two are just mandatory criteria that must be met beforehand?

Also, if you need "both" conditions met at the same time, you might consider something like this.

@iamtaaaro

You may consider reworking your logic to look a little more like this.

@roar Hahaha. Oof. Yeah. I imagine this is extremely problematic if you're dealing with very low timeframe algos and stuff especially. I suppose other than some large news candles periodically, if you were testing higher timeframe stuff, like you said, it becomes less and less discernible.