<div>X.H.FadeInactive:</div>Attached is my previous patch, which seems to have been stranded. Anyways there don't seem to have been any objections.<div><br></div><div>X.A.GridSelect:</div><div><div>* Fixed X.A.GridSelect to be consistent in the way it (now) sorts the shown</div>
<div> elements when modifying the searchString.</div><div><br></div><div> The implemented ordering sorts based on how "deep the needle is in the</div><div> haystack", meaning that searching for "st" in the elements "Install" and "Study"</div>
<div> will order them as "Study" and "Install". Previously there was no ordering and</div><div> when using GridSelect to select workspaces, the ordering was not consistent, as</div><div> the list of workspaces (if not modified manually) is ordered by last used. In</div>
<div> this case either "Study" or "Install" would come first depending on which</div><div> workspace was last visited.</div></div><div><br></div><div><br></div><div>By not having it consistent, it really fucks with muscle memory.</div>
<div>I'm open for other ways of sorting the elements when the searchString is not null, however sorting them in the order of "the depth of the match" seems to be very intuitive, as I (and others I have talked to) tend to write the first letters of the word that is searched for.</div>
<div><br></div><div>--</div><div>Reenberg</div>