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 2:51 PM #224399
I understand. But I won’t be able to justify the transferring back to your development environment, while your base should be that development environment in the first place. So what you kind of stat is that this is your workflow :
- Have/develop some nice system;
- Put that system to ProOrder;
- Delete it from your list of in-cloud systems without saving it to disk first.
- Now have an issue when you want to remove the system from the list of ProOrder systems (but am I right ??).
Everybody will tell me to tell you to do this :
- Have/develop some nice system;
- Save that to disk;
- Put it to ProOrder.
- And delete it from ProOrder when you want.**
**): Ad 4.: Which won’t be in order any more with V13, because you can archive them (and transfer back from there to the normal Not Running systems).
PS: I have been deleting systems from the Not Running area dozens of times. And that was not because I did not like them any more. 😉
10,000 systems I have not as I am not a collector of systems. I create them. 🙂PS: The biggest fun is if you have say 100 Running systems, have the Not Running system’s list full (I recall 250 ?) and then want to Stop a System. But that is for an other rainy day.
11/27/2023 at 3:19 PM #224402Delete it from your list of in-cloud systems without saving it to disk first.
Above is not what I described.
I save all versions and copies of running and not-running systems to disk on my PC and never delete anything … except not running systems > max of 125 in Demo becvause I have no choice because there is no export function available for code of not-running systems.
We are going round in circles, lets leave it and not discuss any further.
If your archive proposal comes about for v13 and has an export (of code with system title etc) function as part of then this will suffice for me.
11/27/2023 at 3:30 PM #224404then want to Stop a System
The limit is not for non-running systems alone.
The limit is for the combined number of running AND non-running systems (150 in Demo) and so you ALWAYS can stop a system from running as it then drops into the non-runing pot but does not increase the total number in the combined running and non-running pot.
12/06/2023 at 2:16 PM #224954I desperately want a ‘Period Widget’ so that I can select Today, This Week etc to see which Sytstem performed the best / worst today or this week etc … see attached for a mock-up
Did you get your Improvements for ProOrder sent off to PRT Peter and did they include a Period Widget for ProOrder?
I’ve sent 2 Suggestions for Improvment to PRT this week so I want to know do I need to prompt PRT re my Period Widget for ProOrder (no need to if you already sent to PRT recently).
12/06/2023 at 2:48 PM #224958Hi GraHal,
I passed everything on to ProRealTime in separate requests. I received back that it was given through to Paris. I did not get separate responses to all.
Why wouldn’t you hand your “Widget” improvement again (yes, you already did that a couple of years ago) to them ? It will end up in Paris via a parallel path anyway.12/06/2023 at 3:10 PM #22495901/19/2024 at 5:42 PM #226600This is what I see show up from the Jan. 17 (2024) version in V12 on PRT-IB.
It adds a tab “Stopped” (in the top) and you can see that we can “Acknowlege” ticked lines, so they will disappear to the Not Running tab.
I did not try this yet, as I am waiting the whole day so far to stop a system when it makes sense.The two lines of contents I have there, is/are not correct (the both lines are about the same system). But this comes from way old stopped systems so hopefully this turns for the better.
01/19/2024 at 5:45 PM #22660201/19/2024 at 8:13 PM #226612 -
AuthorPosts
Find exclusive trading pro-tools on