Discussing the article: "Creating a Trading Administrator Panel in MQL5 (Part III): Extending Built-in Classes for Theme Management (II)"
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
Check out the new article: Creating a Trading Administrator Panel in MQL5 (Part III): Extending Built-in Classes for Theme Management (II).
In this discussion, we will carefully extend the existing Dialog library to incorporate theme management logic. Furthermore, we will integrate methods for theme switching into the CDialog, CEdit, and CButton classes utilized in our Admin Panel project. Continue reading for more insightful perspectives.
It is possible to modify and create new library classes for MQL5. However, since the built-in libraries are shared by the platform, any changes we make to these files may lead to either positive enhancements or negative impacts on the current platform features. In our recent article, we briefly discussed how we edited the root Dialog class color to affect the appearance of our panel. While our theme-switching button successfully changed the text color, it did not alter the panel skin or the button background color.
Through research, we have finally identified methods to safely integrate theme-changing functionalities into the available classes. After successfully implementing these changes, we adjusted the Admin Panel algorithm to align with the newly integrated features.
Theme switching successful
Today's discussion focuses on the process we undertook to achieve the visually appealing panel displayed on the right. The theme colors shown are based on my opinion on color selection during the development; they can be optimized in the code to suit other user preferences, allowing you to experiment with different colors to find what resonates with you. It's important to highlight the key components of our program that contribute to the overall functionality of the panel.
Author: Clemence Benjamin