Those Constants are actually global variables for which the "input" keyword is used. I only know that they go in "Inputs" tab, I am not aware of any possibility to create new tabs somehow.
Pulldown menus are possible, but only those from the built-in types. If you set the data type to ENUM_TIMEFRAMES for example, it will show all timeframes. Or you can use any other ENUM... type... Of course the problem is that those are part of MQL and you must know how to find them and what they mean 
A trade can be opened in the middle of a bar. I mean, trades don't care that bar exists, they are in no way connected to them. But we can get the time at which a trade has been opened and compare the current time with it.
For example: For eact Trade -> check age -> close
This will close a trade when it is too old. But you don't have to do that, because there is Expiration options in Buy/Sell blocks... which basically is doing the same thing.
There is no ready block to close a trade in the beginning of a candle when that trade is old enough. But this will probably make it: Once per bar -> For eact Trade -> check age -> close
MQL4 sees that answer as plain text, there is no XML, JSON or another parser. Really, the only format that I made it available to read is delimiter-separated format, something like this - value1,value2,value3 - if the Delimiter is set to comma in the HTTP block. Then, in Condition you can access value2 for example, if you set Key to be 1 (because Key is the position in the delimiter-separated string if the first position is 0).
Do you have an example project?
1 Jan 1970 = the value of 0. But the closk is 00:33:37, which means that the actual value behind this is exactly 2017 (33 * 60 + 37). I don't know what you did exactly, but you wrote 2017 somewhere where the expected input value is something else
You mean that when you have a custom indicator in one project and you copy that project, the information about the indicator is lost?
But I don't see this EA anymore. I will suggest to make a shared copy the next time... somewhere in Projects in the menu
@mohammad2232 There is no need of AND, just connect those blocks one after another
You can try it. The fact is that Variables are not true global variables. Normal global variables can only equal to a specific value. But in fxDreema, and If there is not some bug, I made it in such a way that if complex value is written, that value is set in OnInit(). In other words, the Variable itself is first defined as an empty variable and then it is modified once in OnInit(). So I expect this to work
By default all blocks are set to the current market. Yes, you actually see empty field and no symbol name is written, but this is what tells the EA to use the current one instead. Only when you manually write something, only then you have specific symbol (market) name.
Only native enumerations. For example, if you define some Constants with ENUM_TIMEFRAMES type, it will have this dropdown.
Bottom? 
I only know one guy that says bottom instead of button - Crazy Russian Hacker from YouTube (he is very funny by the way) 
I think you are talking about the fact that buttons act more like switches, they don't return back to the uncklicked state. This is how they act normally. But yes, I said multiple times that I need to find a way to make them work as true buttons....
This is some PHP type of response, but MQL is very stupid, it doesn't have those complex web abilities. The response that is expected is either plain text or values separated by some delimiter
Your current EA contains 1342 blocks at the moment. There is no chance for me to check how this EA works, this is tooo much for mu stupid brain
So, if you think that some block doesn't work as explected, which is of course absolutely possible, can you make a simple EA for me that contains 2-3 blocks only and that shows the problem directly?
1 - You are the first one to ask such question. In theory you need to compare (Close - BB) with (BB - Low), but I don't think there is a block that can do exactly this. With multiple Formula blocks and Variables it can be done, or with a custom block. As a MQL4 code this is something simple, but sometimes simple things can only be made with multiple blocks in this tool.
2 - No one ever asked me about this as well But there is a block for that - (Re)draw trades on chart. I think it's enough to connect it somewhere at top level, so it can run on every tick. Or it could be enough to run it after Buy/Sell blocks
3 - That Trade even does not mean that you are trading. The "Trade" word here means that the even fires when some trading event happens.
4 - Because blocks are under "on Tick", they run on every tick. At the top we normally put those blocks that check something and below them we put those who do something. When does the process start again? Let's say that all trades are closed - then you have 0 trades and "No trade" would pass. "No trade" cannot pass until you have trades.
So you don't have to create strange loops with blocks. Again, blocks run on every tick! Again and again and again... multiple times pes second probably. The "process" loop is not what you imagine. Everything starts again when certain conditions could pass (for example "No trade" block)
AND blocks are not needed. The fact that 2 blocks are connected one after another is a natural And logic, because if the block above doesn't pass, the block below would not run.
I think that those yellow Alert and Play blocks are better to be placed below the trading blocks. Well, depends on what they say, but I guess that they say that a new trade has been created. If this is the case, you don't have a trade before Buy/Sell blocks are executed, so why Alerting about that?
The right side with those Once and Every blocks... I'm not sure about it. If you are a newbie, you probably don't know how these blocks work exactly. Even I don't have much sense of how they work.
There is some JavaScript error that happens when the file is being read, but I need to find it and fix it. I don't know how long it will take, so if I don't fix this soon, you can just add the indicator's data manually.
It has 2 buffers and these are obviously the inlut parameters:
int TrendCCI_Period 14
bool Automatic_Timeframe_setting false
int M1_CCI_Period 14
int M5_CCI_Period 14
int M15_CCI_Period 14
int M30_CCI_Period 14
int H1_CCI_Period 14
int H4_CCI_Period 14
int D1_CCI_Period 14
int W1_CCI_Period 14
int MN_CCI_Period 14