Program Code not saved (Bug)

Forums › ProRealTime English forum › ProRealTime platform support › Program Code not saved (Bug)

Viewing 15 posts - 16 through 30 (of 35 total)
1 2 3
  • 01/28/2021 at 6:28 PM #159708
    PeterSt

    Correct. Well, almost, because I still have 19 in there and I can’t (or won’t) go with less. But all of the other do not exhibit now.
    It really requires the Backtest button to be used in order to save something in the Editor.

    Ctrl-s on the Main Menu, Save and Exit, Exit answer yes to Save … all won’t save the changes.

    Might it help for researching this :
    When the Editor is open with my unsaved changes (unsaved, just because I know it did not happen yet), and I open the Editor from another instrument again (this happens automatically so), then original instance closes, the new one is brought up and my changes are in there. I did not test whether I can *then* save and exit without using the Backtest button and have the lot saved for real. Also, I think I now will stop attempting more sequences, because it is clear that it just does not work as should. Possibly for the IB version only. Possibly something in my PC. I assume that *or* this will be solved, *or* questions will be asked by PRT for my environment etc.

    Thank you (both) for your help at working this out !

    It is no real issue for me, because I now know and saving is possible anyway (perform a BackTest).

     

    01/28/2021 at 7:12 PM #159715
    GraHal
    PeterSt wrote:

    I can’t (or won’t) go with less

    You do know you can export Algos to your PC (2 seconds) and import from your PC (2 seconds) at any time you need them?

    PeterSt wrote:

    Possibly for the IB version only

    It must be as no IG user is raising any Issues re Algo code editor not saving.  Nor for that matter any IB user??

    01/28/2021 at 7:38 PM #159720
    GraHal

    I’m sorry, I can’t let this go as I want to help you Peter!  You must be doing something different than the rest of us??

    If you are doing this …

    1. Change Algo code in the editor

    2. Leave Editor OPEN

    3. Go File > Quit > Save and Exit

    Then code changes will NOT save .

    If you want code changes to save, you need to …

    4.   Change Algo code in the editor

    5. CLOSE Editor

    6. Go File > Quit > Save and Exit

    When I do 4, 5 and 6 above my code changes are Saved.

    1 user thanked author for this post.
    avatar PeterSt
    01/28/2021 at 8:13 PM #159728
    PeterSt

    When I do 4, 5 and 6 above my code changes are Saved.

    Understood. So you imply that if you leave open the editor, changes are not saved, right ? … Slowly we are getting somewhere.
    I will try closing the Editor as per your description first.
    Tomorrow. 🙂

    GraHal wrote:

    Nor for that matter any IB user??

    But where are they ? they-can-not-autotrade. 🙁

    01/28/2021 at 8:51 PM #159730
    GraHal
    PeterSt wrote:

    So you imply that if you leave open the editor, changes are not saved,

    I’m not implying it … I am categorically stating it!  🙂

    But why would I even expect changes to be saved if I leave the editor open??

     

    01/29/2021 at 6:04 AM #159754
    PeterSt

    But why would I even expect changes to be saved if I leave the editor open??

    And since when would I expect changes to be saved when I close an Editor without saving ?
    But it helps in this case. 🙁

    It is the weirdest I have EVER seen.

    Salient detail is that me myself and I created world’s first “screen editor” (prior to that we had line commands only). How to know that without Internet back at the time ? … easy enough, work in an organisation with 100+ Operating Companies in 100+ different countries world wide (Shell). It spread and in no-time everybody was using it. This was in the era of the Text Processor being invented 2-3 years earlier. If PRT would date from those times, at least I could understand something of it. But still …

    Anyway GraHal, you are golden again.

    PS: This is how v10.3 did it when you’d leave the Editor (cross it away) – see attachment. Now if someone thinks he can outsmart to leave out that message and be faster … Remember what I said earlier on – in V10.3 one could save explicitly. Apparently this is how that worked or how that came to me as “explicit”. Not letting know anything at any time as how V11 now works … No. One could attest that these are the modern ages and that very many software of these days does not ask for saving and does not show OK vs Cancel buttons any more, but that would bear interfaces (GUIs) where you’d expect this.
    I, as a coder may want to undo changes (yea yea, I know about ctrl-z). In 999,999 out of 1,000,000 editors you’d do this by quickly quitting and reopening. “Peter, that’s easy, just leave open the Editor and quit the whole platform. Yes, you are even allowed to save all from the platform itself !”. So please, nobody is going to guess it works like this. Maybe if you are not used to coding …

    01/30/2021 at 10:46 AM #159890
    GraHal
    PeterSt wrote:

    Maybe we must start a topic about what is to be regarded a bug.

    I agree!

    The problem you experienced under this Topic (and now no longer should experience) has not been flagged up by anyone else (to my knowledge). We are all happy to close the editor in order to save code changes.

    If anybody feels same as PeterSt over this then flag it up on here asap please?

    We cannot have a 1 person defined bug set at Priority 1 on the Bugs List?. We need PRT to be sorting more widespread Bugs and even major Wants that are wasting lots of our time trying to make money! 🙂

    01/30/2021 at 11:00 AM #159896
    Vonasi

    I’d say this is a big fat zero on your bugs list!

    I’ve always been perfectly happy that changes to code would only be saved if I ran the backtest/added the indicator or closed the coding window and chose the ‘save changes’ option. I do not need any autosave option and often autosave annoys me in other applications when I make changes that I then decide that I don’t like the look of and want to just forget them. When this happens I much prefer the option to close the window and choose the ‘don’t save changes’ option.

    01/30/2021 at 11:13 AM #159898
    PeterSt
    Vonasi wrote:

    When this happens I much prefer the option to close the window and choose the ‘don’t save changes’ option.

    A vote up for that one. And as I said or implied, with V10.3 I didn’t have any problems with it at all.
    Still, because there’s no explicit save available (what ever can be wrong with providing a ctrl-s in there) I would much later not know to what situation to revert to. For example, when I am coding in there, I may 10-20 times per hour use ctrl-s on the main menu (in vain, as I know by now). Just because I want to secure my spent time and know that what I save and can revert to, is useful for me. I am not going to exit the Editor 10-20 times per hour in order to have its contents saved.

    01/30/2021 at 11:20 AM #159900
    GraHal

    Okay, compromise all round … how about changing this to a WANT and reword the Bugs List as …

    Re-introduce (the v10.3 buttton) – Save / Do Not Save to show at close of Code Editor ?? 

    01/30/2021 at 11:21 AM #159901
    Vonasi
    PeterSt wrote:

    I am not going to exit the Editor 10-20 times per hour in order to have its contents saved.

    I don’t find this necessary. Usually I make a small adjustment to the code and then run the indicator or strategy to test my changes work. Doing this saves the changes. I have never felt the need to close the window on untested changes at any point in all my time using PRT.

    I would say that unless loads of people jump in and say that they have an issue with things working as they currently do then this is just an annoyance to you and no one else. GraHal and I have already said that we are fine with it working as it does – hence it is a zero rating from me! Surely there are much more important bugs than this non bug to spend time trying to get changed?

    01/30/2021 at 12:07 PM #159910
    PeterSt

    Dear people,

    If you deem it necessary to intervene with my consistent (!) reporting about bugs in a software environment with which PRT development already knows how to deal with (because this is in the end “personal” from human to humans), then you should put everything under discussion what I brought up, and / but then I am definitely out. I do this for you / the community, you know. If you know better, then go ahead yourself, or leave it be. I don’t care really. If I did, I had long gone reported my internal list about the very same things. Now I am losing only time on this list.

    Vonasi wrote:

    I would say that unless loads of people jump in and say that they have an issue with things working as they currently do then this is just an annoyance to you and no one else. GraHal and I have already said that we are fine with it working as it does

    Oh wow. Wow wow wow.
    If that’s how it goes, then I can have one feeling only : bail out.
    Maybe you noticed that nobody is responding to anything. So what about doing it for nobody, actually ? And doing it for you appears not to be necessary.

    I hope this soon turns for the better.

     

    01/30/2021 at 12:20 PM #159917
    Vonasi

    When you are trying to fry a lot of fish it is best to choose one or two big fish and concentrate on them.

    If no one is responding to anything it is either because they do not have the issue or have the issue but it does not annoy them enough to worry about or they are happy to use a work around. If you are referring to a lack of response from PRT themselves then this is not unusual. From my experience they take note of all grievances but do not get involved in long discussions regarding them. Behind the scenes they are working hard to resolve all the issues that they feel need addressing. It might be the case that they do not see your own personal issue as an issue that needs solving at all.

    05/24/2021 at 9:26 AM #170234
    PeterSt

    I just ran into a new nice example of not-saving. Notice that this can’t be prevented, no matter that you know how it “works”.

    1. Spend some time with backtesting, that ending with some Walk Forward testing. Especially this latter is quite killing, for eating memory (please remember, the memory leak is a bug described elsewhere).
    2. The Walk Forward obviously runs into troubles because of once (towards the end) receiving the message “The last action you performed required more memory” (similar).
    3. Usually this ends up with the system not being able to even show the resulting statistics, but this time I was lucky (after 2 hours of waiting for the Walk Forward to finish) and it showed.
    4. Because this is always my last confirmation test that a strategy should work, after this I make a “Live” version of it. Notice that this requires a copy with the debug code (like Graph) removed).
    5. As we know that in order to save a new strategy by means of running it at least briefly for BackTest, I tried to do that, but this time nothing happened (this would be the new situation I never rain into).
    6. Because the effort of removing the Debug code is nothing I like to repeat after a hard day of work, I thought “oh well” and made it a Strategy for ProOrder Autotrading anyway. This was yesterday. FYI: This is just running currently. Somewhere late yesterday the platform was closed after all was Saved as usual (like with Ctrl-s).
    7. This morning my copy of the Strategy was nowhere to be found. The big fun : The Strategy indeed runs in ProOrder Autotrade.

     

    So I just had to spend the time of creating the strategy without the debug code after all.
    Nothing was lost this time, but it consumes time.

    It remains correct that if you don’t run a changed code at least briefly once in BackTest, the code will not be saved, whatever you do further (and notice that I am focused on the situation to begin with). Be that you not running the code briefly, or be that the system which won’t do it for whatever the reason.

    ProRealtime Development, please, personally I am still waiting for the explicit Save button for the program code.

     

    05/29/2021 at 12:35 AM #170714
    Gaby

    I understand the frustration as I lost data too (a whole strategy)…. but now I know how to save my strategy changes. Technically I access PRT via IG and using a Window 10 laptop to test and modify 39 Algos.

    CRT+S is not an available function if you are displaying the editor page; but as soon as you move to another PRT page (like the chart or the strategy dashboard) the function is there and it will save everything you have done so far in the editor. Is it logic? No, it is not. I have never seen an editor programme without the SAVE button or functionality. But guys, knowing the trick you don’t need to close any of your windows (not even the editor) or exiting the PRT platform. Just swap to another window and then CRT+S.

    To believe, test yourself: type a change in any of your strategy, move to the chart window, CRT+S, exit the platform WITHOUT saving (to test this) and then re-enter. You will be pleased to see the changes you just made, despite you closed the platform without saving (that means: CRT+S saves your strategy changes).

     

    1 user thanked author for this post.
    avatar GraHal
  • Author
    Posts
Viewing 15 posts - 16 through 30 (of 35 total)
1 2 3

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
color of saved object not recognised
number of bars per chart not saved
platform settings not saved
prt screener code automatic change or not saved
why is ema20 different in indicator program and screener program ?
6 jan 24 prt not available – too long to respond
accountid does not have permission for epic + locale combination
alert not triggered
alert s not working properly
alerts not always triggered

Create your free account now and post your request to benefit from the help of the community
Register or Login