[Genma Saotome]

It's nice that the object list is long but for me the style (long list of potential objects, short list of recently used objects) is actually the opposite of what I prefer (a short list of potential objects, long list of recently used objects).

That is subjective of course... I'm sure other people like the way it is.

Could the two lists be made expandable within the allotted space? In this way everybody "can have it their way" and do so dynamically... expanding and contracting the pair of lists as needed where the total number of visible lines remains the same.

Something similar for the "picked" texture list would be a great help as well. This could also be improved by not allowing multiple selections / icon displays of the same texture.

[Sandy River Tom]

It's a matter of personal preference.
Making list length selectable would serve both sides.

As long as I can find the Object(s) that I want to place, list length duzzent matter.

[Genma Saotome]

Some years back I edited the .dll's for KUJU's RE and lengthened the list so it looks just as Goku has done in his editor. Worked fine but I found I kept losing items off the recently used list that I needed to place. So I went back and made the ref file list much shorter and lengthened the recently used list. It worked much,. much better, especially for track where you are using thr same few track switches, the same long tangents, etc. With a longer recently used list your favorites are just not has likely to drop off as they do with a short list.

Yeah, it's subjective, which is why my request was to make both lists grow and shrink as the user wants. My hunch is that over time people will have a shorter and shorter ref file list.

I suppose another way do doing things is to have both lists rather long but only display a portion of each. The scroll bar takes you to the rest.

[steved]

I would be happy if the list only showed the items you used and not all of the ones you click on to look at.
It doesn't take long looking at potential track pieces to fill the list and push the ones you use off the end.
Separate breakout windows for all of the object, terrain and property side bars would be a welcome development also.
Since Goku released TSRE into the wild I'm surprised someone hasen't taken the ball and run with it.

Steve

[Genma Saotome]

steved, on 23 July 2019 - 06:18 AM, said:

Since Goku released TSRE into the wild I'm surprised someone hasen't taken the ball and run with it.

Steve

The OR team mentioned one issue: They code in C# and Goku used C++. Apparently the differences are a bit tricky\, esp. for non-professionals (like most of the OR team).

Goku's license is Open Source so if anyone wanted to fork it and continue on a different path they could.

[pwillard]

Genma Saotome, on 23 July 2019 - 02:49 PM, said:

The OR team mentioned one issue: They code in C# and Goku used C++. Apparently the differences are a bit tricky\, esp. for non-professionals (like most of the OR team).

Goku's license is Open Source so if anyone wanted to fork it and continue on a different path they could.

"Opinion:"

I applaud the use of C++ over C#. While I know solutions like Mono exist for C# coding on Linux... I would have much preferred a world where migration to the Linux platform would have been within the realm of "SANE" for ORTS. ORTS being done in C# likely means it could never have a Linux option.