v11 bugs

  • This topic has 108 replies, 13 voices, and was last updated 1 year ago by avatarGraHal.
Viewing 15 posts - 61 through 75 (of 109 total)
  • #158796

    Errors are gone again, something annoying and costing money. We have waited so long for version 11, then it should work without errors, after all, this is also about money. 😉

    What happened is :

    1. PRT V11 was made available to the public in an environment where no AutoTrading is possible (PRT-IB);
    2. June 2020 it was given to IG who laid it aside until December 2020.

    And thus nobody could really test it for the AutoTrading environment.

    Kind of official standpoint of PRT is that IG is to be blamed, with “kind of” between quotes. This is because it may be so all right, but *still* it costs money (indeed) and IMHO PRT is responsible for it.

    Even if I filed a 100+++ bugs, there are still so many small ones which will never get attention because at PRT development they say “oh well”.

    I’m going out on a limb here but could this because there are lots of people emailing them duplicate error messages so they are so overwhelmed with sorting through multiple emails that the critical issues aren’t getting looked at?  Maybe some form of collating them in one place for review by Nicolas before escalating them on to ProRealtime might be an idea? Oh wait that’s what we’ve just roughly knocked together. 🙂

     

     

    #158798

    Your given contact links are not the correct ones

    Which links are you talking about?
    Please copy my link with (grahal) after.

    Please copy what you think is the correct link with the word (PeterSt) after.

     

    #158800

    Hello everyone, please keep calm and consider each opinion with respect. We all have a different experience of life and how things should be organised for better understanding by another party.
    Take my word for it, all the bugs reported here on the forum are carefully studied by the ITF teams (who develop PRT), some of them have already been fixed (believe me, I read the dev logs).
    I have provided myself the link of the list of bugs that you had the good idea to create to whoever is entitled to it. It will be followed I can assure you.

    Finally, know that even if I don’t answer each topic quickly, I read them and I ensure the link with ITF/PRT, I don’t want the efforts of the members to improve the platform to be vain!

    Thank you all for your patience and please let’s try to continue to develop good relations between us, sometimes it’s better to keep your fists in your pockets 😉

    3 users thanked author for this post.
    #158805

    there are lots of people emailing them (PRT)

    I could be wrong, but I reckon over 80%, could be 95% of users bash out descriptions of problems on Forums and then get annoyed when next time they feel the bug that it has not been fixed??

    Majority of users do above, but (in my opinion) they don’t email  PRT direct using the correct PRT Forms posted on the PRT website?

    From my observations, many new users even think this website is PRT and so by posting on here (particularly  on Platform Support Forum) they are advising PRT!?

     

    #158809

    you could accidentally click that red cross and lose your position (like my example again and this really happened).

    Yes, above has happened to me also!  I’ve got now so I am afraid to even move a stop level or cancel an Alert etc if there is a manual trade on the chart in case I close the trade (due to the bug in PeterSt quote above)!

    Unbelievable some of the bugs that were not picked up by PRT Testers before GoLive with v11 (2.5 years ago!!).

    1 user thanked author for this post.
    #158810

    I’m going out on a limb here but could this because there are lots of people emailing them duplicate error messages so they are so overwhelmed with sorting through multiple emails that the critical issues aren’t getting looked at?

    Nah, that is not the case. And this is exactly part of the problem …

    IG customers normally don’t have direct contact with PRT support (they can, but they kind of formally need to go to IG with issues).

    Hence, this is all new, albeit necessary.

    For you guys, and for Nicolas too, I *am* working on the getting through of your issues, because some have their ways. For Nicolas this is obvious (so trust him on what he just said please) but for me this is not obvious at all. Unless you can grasp the difference with someone how formally *can* address PRT support with issues. And this is me (which is more rare, because this forum is about ProRealCode and I – working with PRT-IB (not IG) can not AutoTrade. Still I hang around on this forum, maybe because of hopefully more insight on V11 (which I use for over a year exclusively).

    So PRT surely knows about your issues in general, and I explicitly took care that this is taken as “severe”. FYI, I started with this something like 10 days ago. Now it needs the examples. And we are all working on them now. But they, please, should make sense. Otherwise even I am not taken serious. 😉

    For example – and only that ! – see the attachment.

    The first line in there is no bug which requires capacity from PRT Development. Just because we can solve it (sorting sequence). So add a column Prio ?
    The second line is not by the slightest a bug. It should not be in the list.
    The third line is a severe bug. More than. Top-Prio.
    … and so on.

    I suppose we can agree over this ?

    Maybe some form of collating them in one place for review by Nicolas before escalating them on to ProRealtime

    Maybe. But maybe not. I will leave that to Nicolas to answer. My point would be : there is so (soo) many things to judge and know, that maybe no normal human being – who also has a normal job ! – is capable of tracking this. Thus IMO : not necessary. But put in bugs – not solvable things by ourselves (with the help of this forum). Later, when most has been sorted out, we could hop to the less important things, up to the “wants”.

    Kovit, I like to repeat : you did your stinkin’ best to form that list. In case my English is too bad : that is super positive. And also quite necessary. Otherwise it won’t come through to PRT. So I think we should continue the “grabbing” of posts with issues. I still don’t know the format yet.
    Btw, it could be so that Nicolas just said that he already is passing on all (!) the issues – like I do here or there. In that case it is already arranged for. … But is it ? I myself still have my list of 36 topics in the Coding area (yes, I am eager to add to the list !).

     

    #158812

    I could be wrong, but I reckon over 80%, could be 95% of users bash out descriptions of problems on Forums and then get annoyed when next time they feel the bug that it has not been fixed??

    100% my idea about what happens. But this now starts to change … 😉

    #158813

    Agreed maybe there was a lost in translation moment. Unfortunately I had to use the description at the top of each thread for the spreadsheet as I thought it may be easier for the users that initially posted the thread to find but they could be changed so it’s more user friendly and easier to scan through.

    The intention was just to get it started so other forum users feel more inclined to use it but I’m happy for anyone else to add or amend any of the content on there they don’t believe to be correct.

    Also the same with spreadsheet format or methods of input, if anyone has any ideas how to do it better run it past GraHal as he hosts the spreadsheet, there’s a crap load of different expertise in this forum so we must be able to streamline things a little and make life easier for forum users but especially Nicolas and the other moderators.

    1 user thanked author for this post.
    #158814

    The intention was just to get it started

    I’m with you on above and everything else you said in your post above.

    Agile development … we can adapt and change etc.

    We seem to be naturally forming an effective working team including PeterSt and any others who would like to join us?

    #158816

    Your given contact links are not the correct ones

    Which links are you talking about?

    Please copy my link with (grahal) after.

    Please copy what you think is the correct link with the word (PeterSt) after.

    OK, as I said – I have been reluctant to post about this. So I just asked PRT … It would be all right for me to vent this :

    First off, people must realize that the email address (or link on the prorealtime.com web page) ends up at different support pages for the different countries. It is somewhat more complicated because this is about “languages”. Thus, someone following the link in Italy would address a different person (Italian speaking) than someone in the UK. However, the person in the UK may address the person in Holland at the same time. And the person in Germany (if I am right, the person you see appear in the spreadsheet is from Germany – I know them all – haha).

    Is this bad ? No. Sort of No. Because, if a problem (or list) goes to someone in Italy and to someone in UK at the same time (because both don’t speak each other’s language) the same problems end up at different persons. They each may a. try to answer upon it and b. may escalate it to 2nd line support or PRT development. There it may end up by the same dealing department.

    It may be unbelievably hard to get across, but this sort of “mess” actually springs from IG customers never having contact with PRT. You don’t have your accustomed contact person at PRT.

    Anyway, I asked … it is a good thing to have a list. Support will pass it on to 2nd line and beyond. Because they now know about it (apologies if something went parallel from what Nicolas has been arranging for) it should be all right. One thing : this depends a bit on the support in your country. Example : I have been dialling 0044 maybe 10 times over the years, but never received an answer. However, that too should have been arranged for by now, and Dutch support could be answering the phone. Or email.

    One more thing : While I started this said 10 days or so back, today I mentioned “our” list as a work in process. I was asked to send it in so they could look at what we were doing. Under the condition that “it is trial for now” and “it is under discussion”, I sent it. So some balls really start rolling …

    Thank you RaHal. Thank you Kovit. And of course thank you Nicolas.

    1 user thanked author for this post.
    #158817

    I was asked to send it in

    Haha … great stuff … it’s who you know not what you know!! 🙂

    #158820

    I was asked to send it in so they could look at what we were doing. Under the condition that “it is trial for now” and “it is under discussion”, I sent it. So some balls really start rolling …

    Thank you RaHal. Thank you Kovit. And of course thank you Nicolas.

    That’s great news PeterSt, good work.

     

    #158939

    Hi there everyone, I came back after a trading sabbatical to find either the new V11 or the issue I had before with chart templates not saving the last state, is back with a vengeance: Every single template layout that was named and associated with my 50″ monitor (as opposed to my Macbook desktop) have been messed up. By messed up, I mean I originally had two rows of charts with about 5 charts in each row and sometimes a chart or two underneath the top chart for the 50″ monitor. Now when I logged into today using my 50″ monitor for the first time in months all my 50″ templates have charts that are taller than the 50″ screen and are taking up the whole north/south height of the monitor screen and only about 3 can fit across the width of the screen as they are so large now. Some of the charts are literally half showing on the far right of the screen with the rest of the chart offscreen to the right invisible. The  rest of them are haphazardly spread around the screen in random positions, Those 50″ templates and their backups (backups I created, sometimes in triplicate, only because of previous save issues) are now redundant. Months upon months of work getting the chart layouts just how I wanted them has been wasted.

    I also spent about 30 seconds trying to pick up the bottom left hand side of a chart to reduce it’s size but the PRT icon “I_”  would appear for a split second but you can never grab it and actually change the size of the chart.

    Since the v11 “update” I can now not gather all PRT windows on my Mac on one desktop. I have 5 desktops. I believe that the split across two desktops with some charts on one desktop and others on another desktop happened because something is new/different in the way you select templates now and I ended up changing to a different template when I had no intention of doing so just as I was going back to desktop 1 where my Apple mail app is located.  Not sure how to fix that?

    In the past any time a result window or chart ended up on a different desktop — because PRT are the only developer that doesn’t allow Mac users the simple option of dragging a PRT window from one desktop to another, — I used the “work around” of clicking on the PRT icon on the top of my Mac menu and that would gather them all back to one desktop. Right now I have some of the charts on desktop 1 and the rest on desktop 2. Nothing that I do will gather them in on to one desktop, even changing templates resulted in most of the charts on one desktop but a couple on another.  Very odd.

    #158949

    Welcome back Bard!

    Sorry I can’t help … lots of us are suffering from that ‘difficult to grab edges bug’ and a whole lot more bugs besides! 🙁

     

    1 user thanked author for this post.
    #158959

    @Bard, not sure whether this can be helpful (I think not) :

    I suppose in V11 only (meaning, not 10.3) there’s counterproductive intelligence which gathers all on the active monitor, might the other monitor(s) be off for whatever (technical) reason. Off means : not recognized by the Operating System. Regarding this I can have one advice only : when this happens : don’t save ! Exit, sort out some ideas to solve it from the start and only Exit and Save when you are satisfied with the result again.
    But probably in vain because too late, right ? Notice that what you save a first time, also will apply to V10.3 as far as “possible”.

    Or … apply the above (don’t save) and revert to V10.3 while you still can. *And* sort out the issue.

    Or … If you have backups, try whether they still work in V10.3 so you can proceed. Meanwhile I would be a first to help sorting this out. Such issues were already announced by me at PRT, but I could refer to your issue to indicate the severity. THis meanwhile should solve the “a monitor is not recognized by the OS”, because already that makes it impossible to work with DisplayPort video cards (never mind the outlay on that).

    Can you still revert to some working situation ?

    To soften your problem, e.g. yesterday I have been working for 30 minutes to restore my screens from the day before, for the programming (ProRealCode) environment. Only because I started to work with 3 strategies at the same time, the day before and nothing wants to stay where / how I left it. If you have hair left, you will lose it now …

Viewing 15 posts - 61 through 75 (of 109 total)

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