Search results are truncated in the editor

Post reply
Not favoritedFavorited Favorited 0 favourites
  • 3 posts
From the Asset Store
Searching
$16 USD
Searching is a game where you are challenged to find all the images with the requested letter in 30 seconds.
BassoGames's avatar
BassoGames

  • We updated our project from the LTS version to the latest stable and noticed an unwelcome change: search results are now truncated, showing only part of an action or function.

    Our project has almost 20K events, so searching for things is a big part of my daily work. Previously, I could open a list with very long search results and just scan through them to find what I needed — for example, to check the value of a specific function parameter.

    I have two wide monitors specifically for this kind of work, so I can expand the search results list across both screens if needed.

    Now though, the results are truncated, and I have to click every single line just to see what's hidden behind the "...". This slows down my workflow quite a bit.

    Ashley, Could you please revert this change, or at least add an editor setting to disable truncation?

    Tagged:

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • This change was made to fix issue 8932 where showing too much content could cause the editor to become unresponsive or crash. (Take a look at who filed the issue!) The report showed a worst-case scenario where you can have something like 10MB of minified JSON data - with the entire file content on on a single line - then if you search for a character like { you can get thousands of results, each showing a full 10MB file in every listed match (as the match showed the full matching line), spike memory, and then hang or crash the tab.

    The fix was to limit each displayed match to show at most 100 characters before and after the match. Increasing that to 1000 doesn't appear to affect the original performance issue too badly. I've made the change for the next beta so you can try it out, and if that does the job and doesn't cause any other issues, then it's a simple change and we could merge that back to stable/LTS.

  • (Take a look at who filed the issue!)

    Oops :)

    The fix was to limit each displayed match to show at most 100 characters before and after the match. Increasing that to 1000 doesn't appear to affect the original performance issue too badly. I've made the change for the next beta so you can try it out, and if that does the job and doesn't cause any other issues, then it's a simple change and we could merge that back to stable/LTS.

    1000 characters should definitely be enough, thank you!

Post reply
  • 3 posts
Index icon Return to board index
Jump to:
Active Users
There are 0 visitors browsing this topic (0 users and 0 guests)