How about the price? Who pays?
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Helo All!
I've actually added this comment to an older topic before, but since that topic was old, I assume it has no activity so I decided to create another topic, hoping it will get more attention.
I think mql5 has a huge limitation when it comes to clipboard access.
Currently, CEdit, or more precisely the OBJ_EDIT chart object, is practically the only native way developers can interact with the clipboard through copy, cut, and paste operations.
We can use DLLs, but it comes with some major limitations, such as platform dependency, and the mql5 market regulation. A program using DLLs is essentially flagged as a potentially dangerous program (And it is, but I think copy pasting is not).
This becomes a serious limitation when developing applications that deal with large amounts of input or output text. Imagine building a chatbot directly inside MetaTrader 5. You might be able to create a custom multiline text control, but allowing users to conveniently copy long responses or paste large prompts becomes unnecessarily difficult.
I believe either of the following improvements would make a significant difference:
Native multiline support for OBJ_EDIT, ideally without the current text-length limitations. (Currently it is limited to 63 characters)
Programmatic clipboard access, even if it's limited to copying text from the clipboard. Something as simple as ClipboardGetText() would already solve a major part of the problem.
Personally, I think the second option would be even more valuable, as it would give developers much greater flexibility when building custom interfaces.
I genuinely struggle to see a significant downside to exposing such functionality, especially considering how much more sophisticated MQL5 applications have become over the years.
I hope this post reaches the MetaQuotes development team and encourages them to reconsider this feature.
Thanks for reading!