Improvements to Batch Render window

This post is originally coming from the official Enscape forum: https://forum.enscape3d.com/index.php?thread/25196-allow-us-to-enlarge-expand-the-batch-render-window/

The UI Design of the batch render window is very problematic. The latest Enscape version has made it even worse, to a point that it's become useless.

1. The batch render window has a fixed width. There is no way to widen the window. As a result long scene names are abbreviated and the user cannot see which scenes they are choosing to render.

2. In the previous versions of Enscape hovering over the scene names would display their full string in a pop-up bubble. This was the only thing that could help us with this problem. Starting with version 4.0 hovering over scene names in the batch render window no longer displays a pop-up bubble. The user cannot see the full name of the scenes.

This makes the batch render window useless! Kindly providing some solutions, as to how the batch render window can/should be improved:

1. Allow the batch render window to be resized horizontally. This ensures longer scene names will have enough space to be displayed properly.

2. Add a filter search box to the batch render window! Currently the user is forced to either select all checkboxes or individually go down the list checking and unchecking scenes. However if a user wants to only render scenes that contain a specific string (example: render all scenes that contain "Camera 5"), there is no way to target this and the user has to manually scroll down and individually find and check the desired scenes. If you have more than 300 scenes, that's a very counter-productive and tiresome work that wastes your time. A filtering search box would be the most perfect solution. Being able to filter out scenes by typing would speed up workflows tenfold.

3. Bring the hover option back, making sure that mouse-over on the scene names displays a pop-up.

Please refer to the attached screen recording and screenshot for visual demonstration. Hoping this will be taken into consideration and implemented soon, because this problem has significantly slowed down our whole 3D team and we are forced to find other other ways to bypass this. Thank you!