English

[AVT]

Could we add a forum section “possible bugs” or something alike to collect things which seem to be related to a bug in PRT, if obviously correct code does not what should do.

Example: position of the weeks barindex painting which appeared in the Swing Teller discussion.

It would have been easier for me to look into such section and stop wondering why I have the same problem with my code. Would also be easy for others to look up whether a problem was already reported, so it’s not posted again and again. And at least PRT programmers might use it as source of what should possibly be corrected.

Of course one should be very, very careful before crying bug! So if we have here two or three collecting moderators that would be ok. What do you think?

Thanks for your attention.

[Nicolas]

There are already forum threads for this kind of reports:

https://www.prorealcode.com/topic/prorealtime-v10-3-bugs-users-reports/

https://www.prorealcode.com/topic/centralization-of-queries-and-suggestions-on-prorealtime/

Much easier to manage a thread than a complete new section of the forum (and in 5 different languages 🙂 )

AVT thanked this post

[AVT]

Hey that’s great, that was exactely what I was thinking of – immediately bookmarked!

(I really have to learn first how I find things on this site.)

Thanks for being so patient with all those newbies.

[JC_Bywan]

Hi,

I would add that the “v10.3 bugs users report” thread is best kept as a “list of proven bugs” with one message per bug, rather than a place to “discuss if something might possibly be bug or not” with several posts about it, as its initial purpose was to propose a short evolving list to the PRT guys…

In other words, if in doubt if you face a bug or not and want to discuss it, it’s best to first create a separate thread about it (or find an existing thread about it with the forum search engine), and if the conclusion of the conversation proves there’s a new platform bug discovered rather than a users’ error, then you can add a message to the v10.3 bugs users report thread, keeps the list tidy this way.

Nicolas, manel and AVT thanked this post

[AVT]

This is what I meant with “collecting moderators”, a few people who have an overview of all the stuff which is discussed in the forums as possible bug related write a bug report with code snip to reproduce it. Confirmations can simply be done by a Thanks mark and addtions for a bug are only made if a different code snip also confirms the bug or test results are inconsistant.

[random45689]

Can I ask if anyone from ITF are actually aware/looking at those threads as there have been things on there for many months and the list just seems to keep growing and no feedback about progress or any acknowledgment

Also agree not a place for discussions but also don’t think this is the best way to list bugs for a developer to wade through the postings but I guess it’s the best way to do things for now until a better way is implemented (?)

[Author]

Posts