Rules for reporting program bugs on the forum

[admin]

In order to facilitate the follow-up and correction of errors and problems related to the program communicated to us by our users, you should consider the following rules regarding error reporting on the forum: 1) When a program-related error is detected, write it as an additional message to any existing topic Instead, a new topic should be opened and the error should be reported under that heading. The title should describe the problem in general (Example: In the attached project, the program crashes while taking beam drawings) 2) In order to correct the relevant situation, our computers should also be recreated. In this context:

• a) The situation that caused the problem should be described step by step.

  Correct example: open the attached project, enter the properties of the K1 beam marked at the bottom left of the ground floor, set its height to 60 cm, analyze, enter the beam reinforced concrete, the program crashes. Wrong example: There is a problem in beam reinforced concrete.

• b) The relevant project and other files (texture, library, dwg file, etc.) must be attached to the message or sent to the technical service via e-mail.
• c) If there is a visual problem, the problem should be marked on the project or a screenshot should be attached. (Example: If the lb length is incorrect in the beam expansion, marking the relevant beam expansion with a revision cloud)
• d) Only the screenshot is of no use in case of program crashes.
• e) The problematic element must be specified together with its solid and name.

3) Every message written to the forum, whether it is a bug report or a request for new versions, must be is read and considered by the software team. For this reason, repeating the same topic too much will only crowd the forum and reduce the efficiency of the forum. 4) The program crashes, why; Why is the beam expansion wrong? Why is my equipment not recovering? We can't reply to messages like this because we don't know for the moment. In order to find the cause of any problem, we must recreate it on our own computers and examine the cause in detail. (This article is written to reemphasize the importance of 2a and 2b).