You can define 3 Variables "point1", "point2" and "point3" and when certain condition happens to modify them. But it's always best if the indicator can give those values to the EA 
After all, indicators are used for that reason - to give the EA what is needed to trade.
I just wonder how the robot will decide to place "point1" there and not on the previous bottom?
Magic number attribute is used for Group numbers (Magic number=MagicStart+Group) and magic numbers cannot be modified at least in MQL4 - here is the function to modify trade/order and there is nowhere Magic number parameter: http://docs.mql4.com/trading/ordermodify
In other words, if a trade is created with magic number = 1000, it stays with it forever.
But you can always close the N-th trade.
Get this for example (don't try it on Real!), try it on backtest: http://fxdreema.com/shared/CVreVRMR
10 trades are created with ticket numbers 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
I want to close only trades 8, 7 and 6, so in "For each Trade" I skip 2 trades and work with not more than 3 trades. Skipped trades are of course those with ticket numbers 10 and 9.
Group number is used to group trades/orders in the project only when needed. And it's needed when you want to control one group with some rules and other group with different rules. If all trades/order are to be controlled in the same way, then no Group is needed (all should have the same Group).
Group number is associated to the trade/order when it is created. Then it doesn't change in MT4 (but it can change in MT5).
Then, you can have 20 trades, 10 of them from Group 1 and the other 10 of Group 2.
In all the blocks that are designed to load or check certain trades and orders you can choose which Group to work with, so within the same project you can control first 10 trades in one way and the other 10 with another block in a different way. Again, only if really needed.
Maybe I'm starting to understand what you want to do... maybe you want to filter trades by their age, and this can happen using "Start trades loop" block (I just renamed it to "For each Trade").
By default it loads trades starting from the newest (youngest) and it continues to the last trade that has the same market, Group and type as specified. But there are two other options - [Skip "n" trades] and [Not more than "n" trades] - and with these options you can skip and limit trades, so you can for example skip trades 1 and 2, then load 3, 4 and 5. For this set the parameters to skip 2 trades and to load not more than 3 trades.
Maybe this one was not for removing because there is no "Once per barS". My mistake, I will show it again, but in future I will probably replace it with something like "Once per bars".
Well, it is possible in MQL4/MQL5 using ObjectSet function, but I was not added this in fxDreema. I don't know when will I work on objects again (now I work on documentation), but you can try http://docs.mql4.com/objects/objectset
Something like...
ObjectSet("MyTrendlineName", OBJPROP_PRICE2, 1.2345);
or with first checking if the objects exists:
string name="MyTrendlineName";
if (ObjectFind(name)<0) {return(0);}
ObjectSet(name, OBJPROP_PRICE2, 1.2345);
This will execute block 1 first, then 2, then 3, 4, 5, 6, 7, 8, 9, 10: http://fxdreema.com/shared/UAhPkCTub
It's possible, I tend to think that it is javascript problem when creating a new block, and I checked javascript functions many times, but it's truly possible to happen while copying blocks, I have to investigate that.
Now only IDs matters. When the final project builds IDs are considered. Blocks position data is used only to draw blocks on the web page and when copy/paste blocks. Maybe it's better to have an option to normalize IDs concidering their location, so the user will see the result of this immediately and will still be able to position blocks anywhere.
I still don't know why block IDs starts to grow without reason
If needed, "Once per bar" block can be used. It matter if it is located before or after the condition. In one case you have "Once per bar check that condition" and in the other you have "Check that condition (on every tick) and if it is true then once per bar do the next things".
There is also included custom indicator Awesome.mq4, so it can be used as well. It has 3 buffers - one for the overall values and 2 separated for the green and red histograms. Then "Indicator appear" may help.
There is no matter where the block is located, what matters is it's ID number - lower numbers are executed first. Blocks on top level means that there are no other blocks connected to their inputs, or you can imagine that "on Tick" button is a block and is connected to them with invisible connection lines.
But if location makes more sence, I can think about it. I can imagine that blocks have no visible IDs and they are executed depending on where they are - top first, or if they are on the same level - left first. Does this sound like something that should be like that?
In this EA you detect whether the price is above or below the trendline, and it works... no matter if one of both comment messages is not edited.
To detect when it breaks is another story. This means that the price is going from below to above or from above to below. So I can suggest to use crossover: http://fxdreema.com/shared/2HwDQrbAb
By the way I found a little problem using in objects category in Condition when using it this way and I fixed it, so use this example on the web version because it will probably don't work on the local one at the moment.
I think "Indicator appear" will be able to do it, try it with the buffers that represents one of the lines (or whatever they are).
I don't understand why you want to use MA to detect color change of Awesome. Obviously the color is changed when Awesome reverse it's direction, or if you compare 3 candles - the one in the middle is above/below the other two. But what role have MA here?
By the way, blocks with lower number are executed first, so block 1, then block 7, then block 26.
This function gets the value from Awesome indicator: http://docs.mql4.com/indicators/iao It's pretty simple, no indicator parameters at all.
This is built-in indicator and it does not have buffers from which to get color information. It looks that the only thing that one can get is the level.
0 and 1 in the first block, 1 and 2 in the second - it works and some "wrong" signals will appear.
http://fxdreema.com/shared/Xth7sKzyc
It looks that some block like "Indicator changes direction" is needed
Така с Copy-Paste не може, защото не участва clipboard-а, а временната информация се пази във временен файл на сървъра. Но можеш да импортнеш .mq4 или .xml файл в локалната и от там да ги копираш.
I think I want to remove the "start" word from it, and the "start" meaning as well, because in fact all the next blocks are executed "inside" this one, so everything starts with it, happens in it, and also ends with it.
The word "Loop" is used in programming to describe "For" loop, and "For" is used in this block so I used the word "Loop". But now I'm not sure that this word is the best, so I'm searching for a new name.
"Loop trades", "Trades loop", "For each trade", "Load each trade", "Trades: One by one", "Load trades one by one"...
I like "Loop trades" because it sounds simple, but maybe "For each trade" describes it better... 