Program Code not saved (Bug)
Forums › ProRealTime English forum › ProRealTime platform support › Program Code not saved (Bug)
- This topic has 34 replies, 5 voices, and was last updated 2 years ago by PeterSt.
-
-
01/24/2021 at 1:58 PM #159238
Although this is one of the most severe bugs in order, I saved reporting about it until it “bugged” me in real time. And there it is …
In the other topic I just described about the “memory” bug and to quit the platform quickly after saving, so you won’t lose any data. I will now describe two bugs in the same topic because I regard it the same bug, both leading to the same misery – lose data (program code).
- There is no explicit Save Button since V11. I regard this “ridiculous” because you’ll now depend on … what ?
- In combination with nr#1 I just quit PRT and depended on the question Save and “Exit Y/N = Y”. See 2nd Attachment.
I change some small things regarding graphing, which you can see in Attachment 1. What I changed there is not important, but at line 139 and 142 I set those variables to 0. Thus, Save and Exit and … back are the variables to 1.
OK, so I changed them back to 0 again, clicked the main menu, pressed Ctrl-s and …
Now save without exit and the 1’s are back again.
So I now know that THAT is not even saving the code (after using ctrl-s like that a 1000+ of times, just in case after longer typing changes in the Editor (can be hours)).Yes, people reported about these things. I did too (support) a possible 20 time, but nobody is picking it up. Come on …
Then now what you should do :
- Set to 0 again;
- Use the BackTest button (see 3rd Attachment);
- Exit With Save or *now* use Ctrl-s on the main menu (you can now Exit without Save because now the Ctrl-s really saved).
So using the BackTest button causes an internal save, which is not to “your cloud” yet. That requires the additional explicit Save.
Dear people at PRT. Yes, it is me how kept on sending in reports on how the automatic Exit after 18 hours of the PRT platform resulted in anomalies from all angles. Assuming that my PRT Support passed on all my emails and examples about this, you should count 20 over the course of time this dis not work out. What shall we say … 10 months ? 10 months of losing set positions, losing Lists, always needing to set them again ?
Yes, you now managed.I just gave you the most severe example of things not saved in the programming environment of PRT. Just one. About all in there is not save properly or not saved at all. Preparing this example for you takes an initial hour. If it ends up as with the 18 hour exit, it may add 2 days for me. But …
Could you now please look into this yourself ? All of it ? All of the programming environment ?
I think I will make one additional “Bug” entry for you, because all of the other is in a different area. But it still is about things not saved. And somehow only in the programming environment. The normal Trade environment is super (for what I use of it).Thanks !
Peter01/24/2021 at 2:13 PM #15924301/24/2021 at 2:24 PM #159247Press ctrl + s and it will save everything immediately. Or go to the main menu and select “save” with your mouse.
You must mean Ctrl-s on the program code then ?
This is not obvious any more, since the Save icon/button has been removed. But I will try …Btw,
Or go to the main menu and select “save” with your mouse.
If *that* would work indeed, I just added another but, because Ctrl-s clearly shows “saving”. So I tend to …
hahatill soon. But thank you !
01/24/2021 at 2:28 PM #159248Ctrl-s on the program code does NOT save.
XORANDNOT, since you so explicitly say (state) that Ctrls-s works, can you show it ? I showed mine not saving (or should I add more screenshots for even better proof ? not necessary I hope ?)
01/24/2021 at 2:34 PM #159249The code editor now saves any changes intermediately on your computer when you close the editor and it does not ask any more whether you want to save changes. To save such changes permanently on PRT’s system, you have to press ctrl + s after closing the code editor.
01/24/2021 at 2:34 PM #159250Using the menu and mouse (see first attachment) does NOT work (see second attachment).
So please, show yours. And if possible, don’t apply steps in between because that surely may matter (like my BackTest button example, of which is quite 100% logical that it works).
To be sure in the 3rd Attachment my version. It could matter …
(I’m now almost hoping that yours work ad mine doesn’t)
01/24/2021 at 2:42 PM #159256I remember that my system ONCE hung up after a long time of usage and after a lot of memory had been consumed and it did not save any more when I tried to. But this happened only once, and never again. So, press ctrl + s every once in a while and you will avoid any bigger losses of work.
And always remember, most of what we are doing here is meaningless in the long run, anyway.
01/24/2021 at 2:50 PM #159260And always remember, most of what we are doing here is meaningless in the long run, anyway.
I’m intrigued … why do you say above please??
01/24/2021 at 2:51 PM #15926101/24/2021 at 2:55 PM #159262always remember, most of what we are doing here is meaningless in the long run, anyway.
Hahaha. What do you mean exactly ? losing money ? … no man !
Anyway, to be sure … I leave in the bug of not saving unless someone shows me that it works (like I did how it does not). Not tells from theory, but tries and proves.
And oh, I already said it … I too have been under the impression that using ctrl-s works (not on the Edior screen since V11 but on the main menu or elsewhere in PRT with the Editor not in focus), but it really is not so. So that too was theory. A bit costly if I’d lose hours of work.01/24/2021 at 3:03 PM #15926401/28/2021 at 11:49 AM #159662Have you tried editing again PeterSt since you reduced the 40 Algos you had saved / listed?
I just edited some code then exited the Platfrom using Quit > Save and Exit, then logged back in and my changes were there saved (as has alawys been the case).
This Topic is Log 46 on the Wants & Bugs List (PeterSt with a priority of 1 / highest and therefore needs to be changed or even deleted from the List as it is not a bug?
1 user thanked author for this post.
01/28/2021 at 12:33 PM #159670Have you tried editing again PeterSt since you reduced the 40 Algos you had saved / listed?
Not yet, but I sure will. And btw, I did not retry yet because it would still be a major bug. And an even bigger one on top of it because it sneaks in / creeps in.
On a side mote we must be careful because the PRT version for IG is not the same at all vs the one for IB. So if mine still does not save under the conditions tested before (but with less Algos), it well can be that. But lets not speculate.
And … thank you for explicitly testing it !01/28/2021 at 12:39 PM #15967401/28/2021 at 1:12 PM #159681Sorry for being persistent … so you have < 10 Algos saved in the coding area and you made 1 x change in the code of 1 x Algo (from < 10 Algos saved) and then you went File > Quit > Save and Exit?
When you logged back in the 1 x change in the Algo code had not been saved?
-
AuthorPosts
Find exclusive trading pro-tools on