Platform V12 – Your Biggest Annoyance Currently??

Forums ProRealTime English forum ProRealTime platform support Platform V12 – Your Biggest Annoyance Currently??

  • This topic has 51 replies, 8 voices, and was last updated 1 day ago by avatarWim.
Viewing 7 posts - 46 through 52 (of 52 total)
  • #254686

    Referencing your last post in another post just now, from of the moment you posted the above I have been inclined to respond to it – but not sure how in the context of not making people pissed or something in that realm;

    ProRealTime bears the almost technical/strict rule that the more you trade the sooner you are served. So making things new for someone could come down to the same rules set.

    For me, recently things seem to have changed because I now so much work against the limits of the platform – actually over the limits – that matters stopped to be annoyances and merely became hurdles too high. Let’s say that All in my accounts stopped working, and with All I mean All. … I won’t lay out what All actually is in the context for more normal operation, because it is useless to name it and only be negative. But let’s look at the example in the picture below, to indicate in which direction I am talking – and which by now is a necessity. Without that I already can’t work any more. And this comes from all angles.

    While already quite always I deal with things like this – and while my often mentioned 2000+ open tickets are serious reality – we started approaching the ticketing system more from a human point of view instead of from some technical approach which no-single-way works for us (you, me, everyone), but also not for PRT themselves. Read : there must be a reason that tickets never get solved, of which we already do not even know whether they have been solved (the No Release Notes thing). And well, I won’t elaborate how PRT internally deals with this, but let’s say that it is just a stalled system, where the people who try to help you, don’t even know the status (and also cannot get hold of that !).

    For me this now has changed, and the way we are going forward with it, hopefully comes available to everyone. Btw note : I already dropped a “and those poor people from PRT-IG then ?” … which is hardly recognized because no single support person -no matter in what country- does not know one single bit of PRT-IG complaints (or tickets for that matter).
    Btw GraHal, you surely will remember the 100 issues list or whatever we called it (shared in a public Excel), which was handed to PRT three times in the course of 6 months or so, and totally nothing was done with it. So that. And that was only 100 tickets.

    When things finally are being done, we can see / sense / feel, that readily all is overloaded. So Yes, if one starts working on 2000+ open tickets, which are only mine, then where to go. But … suddenly things are really being accomplished, the one you see below being only one of them. Done within a day (really so).

    The message from this post should be : annoyances is one thing, but can not work with is another. And only when the latter are solved, the first may be in order.

    The response I initially – and for fun – wanted to put here when you posted your last post, would have been “But GraHal, then they won’t have time any more to help me !”. It would be a funny remark but with full truth in the background. One thing : all what is being done currently eventually would help all. At least that is the clear stance and btw how I always operate (including that 100 issues excel list). But it never worked out. And today it seems to, suddenly …
    Until further notice ? 🙂

    #254688

    desired functionality which is asked for almost every day.

    We need to ‘up our game’ (somehow) on how we ask for new  and improved functionality.

    A couple of years ago, we (me, you, Phoentz and others??) tried jointly with a ‘Grand List’, later submitted to PRT, but maybe it got ‘out of hand’ in some way?

    I and You (others?) submit Suggestions for Improvement direct to PRT, but if a lone voice then no guarantee of success (see my  previous post above).

    I have had several of my Suggestions implemented, which – I’ll put money on it – were Suggested by myself ONLY (e.g. position change arrows at green arrowhead on attached).  So maybe it depends if any particular submitted Suggestion piques the interest of PRT Developers??

    My opinion is – most on here – think it’s somebody else’s responsibility to advise PRT of shortcomings?  Users make a brief mention on this website (in amongst the text of another Topic) and they hope somebody will pick this up and action it.  This is as far as it goes, no Suggestion for Improvement is submitted direct to PRT.

    Due to above, it’s difficult even to get users to endorse (on here) a Suggestion submitted direct to PRT.

    I Suggested to Nicolas that the new PRC website have a ‘Number of Views’  counter on each post; this to see if even Topics like this one get many views / readings.

    My hope is that – with evidence of plenty of post viewings – I could, for example, ask users to say …

    I  also want the ProOrder AutoTrading window to have
    ‘Average Gain’ and ‘No. of Trades’ to be available as a user-selected column.
    GH01  

    I know let’s try this now as a test / trial …

    If you also want the above Improvement to be actioned by PRT, please just type below and press submit …

    I want GH01.

    Big Thank You for Your Support (for my idea above submitted in July 2024 direct to PRT)
    GraHal
    Hope You All Have a Good Christmas!

     

    #254797

    I know let’s try this now as a test / trial …

    Oh well, does nobody (else?) want Average Gain as a column in their Running ProOrder Systems?

    United we stand, divided we fall …  PRT have said they are more likely to respond to collective calls for Improvements.

    Average Gain is an easy quick way to ‘get a feel’ for how a System is performing … showing against each System means Detailed Reports do not need to be opened for each System to see Average Gain.

    Btw … the screenshot attached to my previous post is nothing to do with my Average Gains Suggestion for Improvement (just in case you are confused?)

    Feel free to ask any questions for clarification or make comments.

    #254869
    Wim

    What I do not like with PRT/IG: ProBacktest uses the time zone you have chosen for your chart. ProOrder uses the London time zone. As long as your strategy only uses price action, moving averages and stuff like that, no problem. But as soon as your strategy uses daily (or weekly or monthly) close values, your backtests are no longer representative of what ProOrder would have done in the same period. This goes for PRT/IG users outside the London time zone of course.
    I would prefer that ProOrder selects the time zone of my chart as does ProBacktest.

    #254870
    Wim

    Small addition to my previous post:
    The impact of “using daily close” in your strategy implies also the use of Pivot Points (daily and higher), VWAP, etc. All indicators that rely on the timing of the daily close.

    #254871

    I would prefer that ProOrder selects the time zone of my chart as does ProBacktest.

    My Platform does as you state above, see attached for my TimeZone Settings.

    #254874
    Wim

    My Platform does as you state above, see attached for my TimeZone Settings.

    This goes for your “live” charting and ProBacktest, but not for ProOrder.
    I had a strategy for which the live results didn’t match the à posteriori backtest. My chart time zone equals the Paris time zone. I than started the Forward Test (I mean ProBacktest on a live chart) and witnessed different trades between Forward Test and live strategy execution. The strategy was based on daily, weekly and monthly Pivot Points. My conclusion: ProOrder calculates other levels than ProBacktest. There are numerous posts in this forum explaining encountered problems with stating that ProOrder uses London 00:00 as the beginning of the day wherever you are on this world.

    1 user thanked author for this post.
Viewing 7 posts - 46 through 52 (of 52 total)

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