search your problem

This is a dummy issue, not really a problem report.

You probably found this, because you selected the Report a Problem menu option on RIDE. The purpose is for you to really do a search to see if your problem is already reported and if is open or closed.
There is a feature on GitHub that allows us to define Issues Templates for the reporting of problems. Well, I think that users of RIDE are Software Testers, so they should know How to do Good Report Issues.

Here are some examples of information you can provide:

• The Operating System (including processor architecture)
• Python version
• wxPython version
• RIDE version
• What workflow/steps did you performed to observe the problem?

You may also consider first talking about your problem in our Forum or in our #ride channel on Slack (see README how to join).

These are known Issues (no need to report them) on current Released Version 2.0.8.1:

• _On Windows - When working with test suites directories/folders, you may see the pop-up of modified files (but they may have just been accessed). Recommended to accept reloading the project, to avoid loss of possible changes.
• RIDE DOES NOT KEEP Test Suites formatting or structure, causing differences in files when used on other IDE or Editors.
• RIDE is not tested in Python 3.12, but known to work in Python 3.11 down to Python 3.6 (although not tested recently).
• RIDE may not be compatible with wxPython 4.2.2 or 4.2.1. Known to work OK with 4.0.7.post2.

See Release Notes.
You can update your package, with: pip install -U https://github.com/robotframework/RIDE/archive/v2.0.8.1.zip.

--

(Hope for one day we have only this issue open)

The issue names GitHub issue templates, the README, and doc/releasenotes/ride-2.0.8.1.rst, but identifies no file or test to change. Start by reviewing those references and the Report a Problem flow; done cannot be verified until a concrete documentation goal is defined.