Block ID numbering

[james]

I have 108 blocks in my EA. I've been doing quite a bit of editing on it, and have let the block numbering take care of itself.

The lowest numbered block currently is 13, and the highest is now up at 260243 - although I'm sure I haven't done that many edits!

Oddly, when I click on it to edit, I see this:

The last 2 digits seem to be missing.

This isn't really causing me too much trouble just now, but I did wonder, would you be able to produce an automatic re-numbering option in fxDreema, just in case it ever did?

Thanks again.

......
Clipboard02.jpg
Clipboard03.jpg

[fxDreema]

I know about this problem, but I was not able to find what causes it, because I never had it on my projects. I can see it on other people's projects, but when you see it it's too late to understand how it started.
I think all the numbers are there, they are just hidden. Can you tell me when this problem started for this project? And how old is this project?
Looking at the code everything seems ok, but I'm probably missing something and I don't know how to replicate this.

That idea of blocks re-numbering is very cool, I'm gonna add it to my to-do list.

[james]

The initial project was started several months ago; 3 or 4 I think. I didn't keep a log, so I'm relying on memory - not always good with me! However, I think I began noticing block numbering jumping from the 90's to maybe the 200's, then up to 400's and 600's, then another jump to the thousands, and just in the last day or so, the hundreds of thousands.

Maybe the thing you are missing in attempting to replicate is copying and re-importing {project_name}.mq4 files.

This happens in two instances:

ONE: When you produce a new local version. Rather than over-installing it, I put each one in its own sub-directory. I mentioned this a little while ago in an earlier posting. Therefore I have, on my disc:

*C:\fxdreema_037
C:\fxdreema_044
C:\fxdreema_047
C:\fxdreema_048
C:\fxdreema_052
C:\fxdreema_053[/list:u:r0o5j2ld]

All my projects are stored in C:\MetaTrader 4\experts, regardless of which version created them originally.

So, when you release a new local version, I install it as above, and then do a "Load project from file" within the new version. Thus the {project_name}.mq4 file arrives in the database of the new local version.

TWO: When I want to move a project on to another version, preserving an older version as a {project_name}.mq4 file, I copy it thus on the hard disc:

*{project_name_v1}.mq4
{project_name_v2}.mq4
{project_name_v3}.mq4
etc.[/list:u:r0o5j2ld]

Then I import the newest version into fxDreema using "Load project from file". I might do this several times. So far I seem to have gone up to 9.

Maybe this importing of the .mq4 file is the missing link with which you'll be able to replicate the issue.

I'm glad you like the idea of a blocks re-numbering routine! I did have one further thought just to mention on this - and I'm sure you've already thought of it, but here goes, just in case! - I have a couple of "Turn ON/OFF" another block blocks, and somehow this would need to be picked up by a re-numbering routine. As I say, I'm sure you are ahead of me on this!

Many thanks.

[fxDreema]

Now Turn ON/OFF blocks are not edited when you change block ID, I know I have to make it happen. By the way block ID's can be text, not only numbers, so you can give unique IDs to be controlled from Turn ON/OFF, but use latin letters only, numbers and "_".

Why don't you just backup the old build by copy it somewhere. All the projects are stored in Data subfolder, and their data size is relatively small. I think it's always better to copy the database itself.

[james]

OK. Thanks. I'll bear those tips in mind.