Improvements for ProOrder ?
Forums › ProRealTime English forum › ProRealTime platform support › Improvements for ProOrder ?
- This topic has 38 replies, 4 voices, and was last updated 10 months ago by GraHal.
-
-
11/27/2023 at 10:52 AM #224369
Export from the ProOrder form would be very very useful!
Currently there is no way – apart from copy and paste – laborious and sooo ‘old skool’ ! – to save Systems from the ProOrder window.
I am constantly deleting Systems from the ProOrder form when what I want to do is to export the systems to my pc and save in a folder called ‘ex Test’!
This will be solved by an “Archived” tab. Or at least that is the intention.
That would work, right ?11/27/2023 at 10:56 AM #224370It would be good if Notes we enter during backtesting and code editing (behind the ? at top of code editor window) could be available / shown / transfer over to the Comments box (was my Suggestion from about 2 years ago) which we now have in the ProOrder window.
I think this should be worked out further because it looks similar to “comments” I deem necessary myself (like for the Parameters).
Can you support this with a couple of screenshots including useful comments, so that I don’t need to guess and may guess wrong ?Following this we may work out more necessary stuff regarding “comments”.
11/27/2023 at 11:16 AM #224372That would work, right ?
Provided we can export individual Systems from the archives?
But if archives gets binned or stretched out to v14 then a simple export System option from the ProOrder form for v13 would be good soonest and may be loads easier for PRT to implement and so therefore may get the go ahead for v13?
11/27/2023 at 11:21 AM #224373“comments” I deem necessary
V12 has a comments box but you may not have realised?? We have to tick a box to show comments.
If I’d been on the PRT dev team I’d have made the comments box enabled by default as it is anew feature and folks may miss it!?
11/27/2023 at 11:44 AM #224375Can you support this with a couple of screenshots
Attached image 1 text in ‘description box’ (on code editor form) transferred automatically as image 2 text in Comments box (on proorder form).
11/27/2023 at 12:19 PM #224378Funny! As Peter I was confused also with your request and it´s because that colum “Comment” in the second image doesnt´apperar in my ProOrder form, and its not an option to include in the configuration neither
11/27/2023 at 12:22 PM #224379We are all talking v12 aren’t we? Have you clicked on the wrench … Comment is top left under Other … 1st one on the list … see attached.
Maybe PRT gave the Comment column / box only to me as I suggested it about 2 years ago! joke 😉
11/27/2023 at 12:35 PM #224381Yes. But see the attachments and especially the comment in there.
Still Yes.The comments I am merely talking about are shown in the third attachment. Or the place I’d want them. No, NEED them. See the fourth attachment;
If you look more closely, you can see that the changes in there are often consistent for dates of applying them. I know I know, most people omit comments in program code, by I coincidently don’t an act the opposite. In this case I carefully register what I changed when and often why. And now the thing :When we move the assignment of variable values to the Optimization Parameters because they are just suitable for it and allow for quick changes of the whole bunch in again some consistency, then the comments can’t be in the program any more, because the values are not there any more.
So what I point at in the third attachment, is a description all right, but it is not suitable for reading (not via editing nor via hovering or something, which surely *does* work nicely with the text from the second attachment (which also is at a line level, like with the Parameters).Summarized, all is about right already, but because it is “about” only, it is not suitable for anything really. OK, this is the case for me.
11/27/2023 at 12:38 PM #22438611/27/2023 at 12:44 PM #224388But if archives gets binned or stretched out to v14 then a simple export System option from the ProOrder form for v13 would be good soonest and may be loads easier for PRT to implement and so therefore may get the go ahead for v13?
Grahal, back to this one … I am not sue I understand this properly. See below.
I must assume that you know about that button, which exports to Excel if you want. OK, what comes from it is quite unworkable (try it if you did not already) but at least it exports (the whole lot – Running and Not Running into one sheet and with numbers which can’t add up, like in most of the Export places)Now what do you mean with the wish for export ?
(and apologies if I just missed it)11/27/2023 at 12:50 PM #224391One of the most desirable things for myself is something which coincidentally worked after a half-failed July 2022 upgrade (GraHal may recall) : letting stay the Detailed Report from a Backtest Result line. Thus don’t erase the previously asked-for version – just create a new one.
I must have made a million screenshots by now, so I can compare with the upcoming version.I did not ask for this yet, as the possibly improvements are merely about the ProOrder form, but I would love those Detailed Report forms to stay. I can always cross them away, right ?
And it worked a couple of days like that ! 🙁11/27/2023 at 12:52 PM #224392We are all talking v12 aren’t we? Have you clicked on the wrench … Comment is top left under Other … 1st one on the list … see attached.
Ok, I am in v11.1 yet. I guess that is why I don´t see it 🙂
11/27/2023 at 12:59 PM #224394Now what do you mean with the wish for export ?
Export individual System code just like the export function available from the code editor.
I want to export system code from proorder to my pc and save the code in a folder.
11/27/2023 at 1:26 PM #224397OK. But what will be the difference with the normal program code ?
The only thing which can be different IMO (!) are the parameters you gave it at startup. But these won’t even copy to a new system (there’s a button for that somewhere, but that doesn’t work and PRT refuses (literally) to solve that.Or are you saying that you amend the normal program code to something else without copying it to a new code first ?
Then I’d understand the wish. But …
😉11/27/2023 at 2:00 PM #224398You are maybe at 1 extreme and I am maybe at the other … you deal with / code / edit / test only a handful of Systems whie I have the maximum at any one time on test … 100 running and many 100’s not running with > 10,000 (counted a week go) stored on my PC. 1 System often has 3 or 4 variants.
I hate deleting anthing as one fine day I may add an improvemnt or improve my coding knowledge and could go back and get a losing System into profit etc.
With a limit of 125 on not running Systems, I have to remove or delete … this I hate to do so being able to save back on my PC asd ex-test makes it easier for me.
In summary, export from proorder form makes housekeeping and cross-matching back to the original / normal program / code lots easier and more user friendly.
To achieve the same -without export from proorder – I would have to transfer the normal systems (as you refer to) from my ‘under test’ folder to my ‘ex-test’ folder before delete from proorder … I have tried this but it’s too much faffing and never gets done when one is pushed for time with the rest if ‘life’s pulls’.
It never gets done because when I need to delete, I am up against the ‘125 limit’ and so I delete 15 or so systems at once so the alternative would be to cross match 15 or so systems and then move from under test to ex-test … big time consuming faff!
Hope above helps with ‘reasons why’ needed etc?
-
AuthorPosts
Find exclusive trading pro-tools on