Hi,

I really appreciate the great work you've done with FXDreema — it's an excellent platform for developing EAs visually.

I’d like to suggest a useful feature: the ability to add custom preprocessor directives such as:

#property (for defining EA or indicator properties)

#include (to include external .mqh libraries)

#resource (for embedding images, sounds, etc.) (To upload an image and use it in the Draw Image block)

These are essential when trying to expand or integrate advanced MQL5 features into FXDreema-generated code. Currently, there doesn't seem to be a way to inject these lines at the top of the .mq5 file from within the platform.

Even a simple text box in the project settings to insert these directives before the OnInit() or OnTick() function would be extremely useful.

Would you consider adding this option in a future update?

Thank you again for your continuous support and great tool!

@jstap Thanks for the shared project, but honestly I didn’t fully understand it. I couldn’t really grasp how it solves the problem.

Could you please explain briefly what part I should look at and how it ensures the block only activates when my bool variable is true?

@jstap Got it, thanks. So that means it’s not possible to make the block check a bool before activation using that box, right?
And the only way is to put a condition block above it?

Hi everyone,

In fxDreema, I have a block with the white activation circle (the checkbox trigger). I want this block to activate only if my boolean variable Oner is true.

I wrote the condition directly inside the small input box next to the white circle, but it didn’t work and the block still activates.

What is the correct syntax to make the block check Oner == true before activation?

Thanks!

@jstap

What I mean is that there is no dedicated feature to define a standalone void function once and then simply call it anywhere in the code.

In practice, especially in Custom Code blocks, logic has to be inlined or tied to block-generated code. There’s no clean, user-controlled place to define reusable functions.

And if you want to add things like #resource, #include, or other preprocessor directives, there’s also no guaranteed global header section where these can be safely defined and managed.

That’s the limitation I’m referring to.

@jstap That’s true — custom blocks are very useful for logic.

However, some things cannot be done with custom blocks:

• #resource must be declared at the global preprocessor level, so it can’t be used or defined via custom blocks (which means images/sounds can’t be embedded this way).
• Custom blocks also can’t define true reusable void (or other) functions — they only generate inline code.
• The same limitation applies to #property and #include, which must appear at the very top of the .mq5 file.

So while custom blocks cover many cases, they don’t replace proper support for preprocessor directives or custom function definitions.

Hi,

I really appreciate the great work you've done with FXDreema — it's an excellent platform for developing EAs visually.

I’d like to suggest a useful feature that would greatly enhance flexibility for advanced users: the ability to add custom preprocessor directives directly within the platform, such as:

• #property (for defining EA or indicator properties)
• #include (to include external .mqh libraries)
• #resource (for embedding images, sounds, etc., for example uploading an image and using it in the Draw Image block)

These directives are essential when trying to expand or integrate advanced MQL5 features into FXDreema-generated code. Currently, there doesn’t seem to be a way to inject these lines at the top of the generated .mq5 file from within the platform.

Even a simple text box in the project settings that allows users to insert custom lines before OnInit() / OnTick() would already be extremely useful.

Additionally, it would be very helpful to have support for defining custom functions (e.g. user-defined void functions) directly within FXDreema, so they can be reused across blocks and called from different parts of the logic. This would significantly improve code organization, readability, and scalability for larger projects.

Would you consider adding these options in a future update?

Thank you again for your continuous support and for creating such a great tool!

Best regards

@fxDreema
@jstap
@l-andorrà

@l-andorrà ?

@Dr-Amiin ?

@l-andorrà When will you do this and if there is any news, please let us know.

@l-andorrà Even a section to upload icons for the bot.