[patch] Schedule list filter improvement

[swed]

Hello !

With a complex network and a lot of lines, using the 'schedule list' window is a pain, cause list contains too much lines, even when filtered by transport type using tabs.
I actually use this small patch, which allows me to filter the list by line name too, using the textinput below the list (see screenshot as an example).

For me it's very useful, but maybe not for everyone (depends how you name your lines...).
Hope someone will like it

Bye !

[Fabio]

Sweet!!

Could it use wildchars * and ? in order to specify if the string sought is at the beginning, at the end or in the middle?

[Markohs]

This is a very nice improvement, I think it should be incorporated in simutrans.

[swed]

Could it use wildchars * and ? in order to specify if the string sought is at the beginning, at the end or in the middle?

Actually, line is displayed in list if his name contains the filter string (as screenshot shows).
I think implementing wildchars */? will be less user-friendly (some players don't even know wildchars).

[VS]

As long as wildcard characters can be part of names, it would be a... complicated relationship

Very useful patch

[Markohs]

Wilcards can be useful to refine, but even without it whould be super useful. It's not that common people having more than 80 lines I guess.

[ӔO]

Wilcards can be useful to refine, but even without it whould be super useful. It's not that common people having more than 80 lines I guess.

the bus lines can get quite crowded if each city gets at least one line...

[prissi]

But it very much depends on the playing style of a players. Maybe rather a filter where you select a station by a combobox of sorted halt names? (Of course onyl those hailed by one of the lines in that category? That would be independent from the name.

[jamespetts]

This is a good idea - I like Prissi's version in particular, since, as he points out, not all players will use naming conventions with which this will be useful.

[Carl]

I agree with jamespetts and prissi -- checkboxes for stations would be the best implementation of this incredibly useful feature.

That said -- is there any reason why the filter could not have both checkbox and text-search options? (to be used separately, obviously)

[prissi]

Too many stuff in the UI. THis dialog is unfourutnately already a monster.

[Carl]

True. In that case, of the two the checkbox dialog would be most useful.

[swed]

Maybe rather a filter where you select a station by a combobox of sorted halt names?

Aim of this patch was to find a line quicker/easier, instead of scrolling scrolling and scrolling again in a huge schedule list containing a lot of lines.
Personally, i won't use a combobox containing something like 100 halt names, or more. It's the same problem, the halt list will be crowded and unusable...
But, as you said, it depends on playing style ; some players may prefer like that.

[Markohs]

 The grep-style original solution is the more oseful one. It whould be perfect if it searches line descrpition AND station list, google-style.

[Zeno]

Too many stuff in the UI. THis dialog is unfourutnately already a monster.

What about splitting in two dialogs? Leave this dialog as a simple line listing, with filtering; nothing else. Then a small button next to each line to open the "manage line dialog", where only a single line would be managed.
It's a mess having to split dialogs (we can end up with zillions of them), but some times might be better. The worst thing is that buttons in other dialogs such vehicle or station would have to be redirected...

[MagnusA]

One way to get a somewhat limited list of lines is through the Station detail window. That window gives the lines serving that particular stop (and the lineless convoys serving that stop as well).

I haven't found any such list on the city level though (lines serving a particular city, i.e. have stops within the city limits). In my opinion, the town hall window would be a natural place for that (if that list is desirable).

[wlindley]

The search-match text (grep) is useful here.  The Combobox function, we already have (the list of lines calling at a station, is listed in the station's infobox).

Given a matching function, the documentation should be updated to encourage players to adopt naming policies; several examples should be provided in the docs.

[Fabio]

The right part could be split in 3 tabs: stations, vehicles and stats.
The first one will have the stop list, edit line button and delete line button.
The vehicle tab will have vehicle list, withdraw all button, withdraw obsolete (new) button and add vehicle button (new: it will open the depot nearest to the first station in schedule and select the line).
The last one will have the graph with its legend.

The left part will have only the lines list, the filters and add line button.
The tabs could be dropped and shown as filters (buttons with the transport type icon).
There could be a filter by name and a filter by station names.

[prissi]

About scrolling in long lists:
One could sort stations also but waiting people+arriving+departing. THus list at most frequented stops would be top.

[Bughu Baas]

The original grep style search window from swed would be great for me - I name my pax lines after the city they are serving, and just enter "Berlin" would give me all lines in that town.

But may I suggest another small but usefull patch?

In the station window, all waiting people (or goods) are shown, including their destination. Lets assume, 12345 people are targetting "Berlin Land 16 H".

But where the f*ck is "Berlin Land 16 H"? Neither there is a triangle button left of it, nor is the text line clickable. So you have to scroll around your city to search for that particular station (to find out which lines are running at that place and why the heck all these buses and trams can't shovel around the people).

[jk271]

I support original swed's version with (some subset of) regular expressions too. I usually use non-default names for {tram|bus} city lines.

[sdog]

a combobox containing the station name is a bit bulky and gets as more unusable than the line list, there are usually more stops than lines.

but having the string search as swed implemented also work on station names, not just line names would be extremely useful.

filtering for london should bring also all lines calling at a stop containing london
filtering railway station in a road vehicle list would also be useful, as it would show all lines connecting to a railway station.

[wlindley]

Works wonderfully but why is it case-sensitive?  filter "train" does not find "Train" ...

[Dwachs]

Try to filter for 'rain' and the sun shines again