Bugs fixing project and two new extra features implementation in MT4 (EA) in existing tool

Description file in attachment.

Price can be little negotiated further. Please read the following text entirely.

Firstly and MOST IMPORTANTLY: Please do some backups, when you will be doing this bugs fixing project for me. I need you to NOT anyhow edit any piece of the code unless absolutelly 100% required in order to create what I am requesting. Basically everything, except what I am requesting (probably less than 0.1% of the code), MUST remain untouched. Please respect this.

I am looking for expert with experiences in the most complex possible bugs (technical problems) in existing tool for MT4. Someone, who perfectly understands that development code needs to be understood in smallest possible details before 100% correct decision can be done: Which small piece of the entire development code is related to particular single feature, out of A LOT of other features. which is a subject of a bug as it doesn't work exactly how I want.

So I would need bugs solving expert who really has surgical accuracy when it comes to being 100% sure that correct part of the code is related to the feature causing the problem. What I am the most worried for is that you would edit something what is unrelated to particular feature with problem (bug). There are so many features. So again: kindly take care that you track correct relevant piece of development code which I will send to you if you decide to contact me.

I have permission from the developer to share this entire development code with expert who will be willing to check the problem. Developer who created that tool for me spent a lot of time and efforts working on the tool. There is massive amount of features in the code. Almost all of them work perfectly, exactly how I want.

Extremely brief description of entire tool is the following (I said extremely brief because I could have written a book about it): I search for single currency which can be either on the left or on the right side of currency pair symbols. Single currencies like btc, xau,... are considered as currency pairs too and some currency pair may have or may not have additional symbols of characters in the title of the trading symbol (e.g. ABC/DEF or ABCDEFpro,...). Tool goes through entire Marketwatch and provides list of currency pairs (single currency either on left or right side of symbol title). I also get information like minimum buy stop distance, minimum sell stop distance, take profit price per point based on my user input on amount of money <currency on trading account is automatically recognized>, stop loss price per point based on my user input on amount of money <currency on trading account is automatically recognized>, amount <currency also auto recognized> of money how much is 1 point profit & loss worth, possibility to open stop pending orders with either minimum required distance (or increase distance) where I clearly define for how many points EXTRA (so minimum plus what I define) must be stop pending orders placed away from current market price. Besides this, the information, that is the same for all currency pairs that I want to place pending orders for, is (by ''is'' i am referring to ''information''): magic number, lot size, trailing (in unit points), slippage (in unit points), take profit (currency auto recognized from logged in trading account balance), target loss (currency auto recognized). Those two take profit and target loss I define in amount of money as I previously said. I enable/tick the checkboxes near currency pairs that I want to schedule placements of stop pending positions. Extremely important for you to be aware of is that every single time when stop pending placements (by ''placement'' i mean opening of stop pending position) happens for strictly only checkbox ticked/enabled currency pairs, TWO (2 !!!!) stop pending orders are placed. One stop buy and one stop sell. ALWAYS TWO! Always those one that I said: one stop buy and one stop sell. Strictly only those two per one ticked/enabled (checkbox) currency pair. Then in the tool I have the option whether I want to make placements immediately upon clicking and confirming Open Trades button or on exact date+time (no limit how near or how far in the future) where timezone is predefined. Obviously tool must run at that time in order for operate. So at requested time stop buy and stop sell pending order(s) get placed. The main point of the tool and the most important thing is the following and due to extreme importance, I will type it in capitalized letters: WHEN ONE STOP PENDING ORDER GETS EXECUTED, THE OPPOSITE ONE MUST GET (and it successfully does!) ALWAYS IMMEDIATELY (HERE WE MAY TALK ABOUT MILLISECONDS OR EVEN NANOSECONDS - DEPENDING ON INTERNET CONNECTION) AUTOMATICALLY CLOSED WHILE BEING PENDING SO IT GUARANTEED NEVER GETS EXECUTED BUT AUTO-CLOSED INSTEAD. Example: if stop buy gets executed, stop sell of the same identical currency pair is automatically and immediately closed (cancelled) or vice versa: if stop sell gets executed, stop buy of the same identical currency pair is automatically closed (cancelled). Identity of currency pairs are verified per trade opening (placements and usage of Open Trades button) event. Having said that, this means the following: Lets say I open ABCDEF currency pair. Two trading positions will be opened (pending): one stop buy and one stop sell. Then a second(s) or some time later I schedule the opening of ABCDEF again, either to be immediately placed (opened) or on particular date and time. So what happens is that one stop buy order and one stop sell order gets placed. Assuming that one out of two stop orders on first opening event hasn't been executed yet (other one auto-cancelled), I obviously have four stop pending orders (same said currency pair): two stop buy and two stop sell. One stop buy and one stop sell is related to first opening event, one stop buy and one stop sell related to the second opening event. When one order gets execute, the opposite one of strictly only THE SAME SINGLE opening event gets auto-closed. So in that situation I remain with two stop pending orders. In, fortunately, extremely rare cases, the opposite order which must get, as most important feature in my tool, auto-closed (cancelled) may not be possible to be closed due to whatever reason: mostly related to the broker (e.g. ''price is too close to the market price''). In case if it cannot be auto-closed then there is already implemented additional feature, which takes care for all the time closing reattempts until that stop pending order, which remains being pending, is successfully closed. Similar logic for prohibited closing for executed orders (based on TP, SL, Trailing): auto reattempt of closing is already implemented. Available currency pairs can be listed on one or on multiple pages: depending on how many of available trading assets have single currency on either left or right side of the symbol.

This was extremely brief description of entire tool. If you need longer, let me know. However, I need to say that I need your help when it comes to bug solving for extremely small piece of code because (almost) everything works fine.

What I need is described in attached file:  described bugs to be solved that are related to graphical fonts (un)wanted (depending on situation) change to ''0'' in exact areas of the tool as described on the video (link to the video is in ''first task'' TXT file) and also new implementation for scratch of two new features. One of them is, I admit, very complex. Note that those two new features have NOT yet been started. Nothing in the code is related to them yet. So I would need you to develop from the beginning those two feature and integrate them to existing development code which is NOT your own (haven't been created by you). As I said multiple times, extremely important is that everything in the code really remains 100% untouched UNLESS it is REALLY guaranteed required to be edited in order to do what is attached in the file. When it comes to integrating two new features, obviously you won't edit any code because your own piece of the code, related to new features, will be new.


For any questions, you are very welcome to ask. Thank you very much in advance.