summaryrefslogtreecommitdiff
path: root/editor/find_in_files.cpp
AgeCommit message (Collapse)Author
2018-11-05Added "shader" filter to "Find in Files"Michael Alexsander Silva Dias
2018-11-05General fixup of the "Find in Files" dialogMichael Alexsander Silva Dias
2018-10-09Improve the editor's Find in Files functionHugo Locurcio
- Disable Whole Words and Match Case by default - Hide the Cancel button once the search is completed - Pad line numbers to the right for more readable search results
2018-10-05Fix Find in Files font size on hiDPI displaysHugo Locurcio
This closes #22692.
2018-10-02Merge pull request #22220 from Naryosha/dialogRémi Verschelde
Fix find-in-files and go-to-line dialog (partially)
2018-09-25Tweak some editor texts' capitalization, use "Go to" instead of "Goto"Hugo Locurcio
This also fixes a typo in the `debugger/debug_with_external_editor` shortcut.
2018-09-18Fix find-in-files and go-to-line dialog (partially)Poommetee Ketson
2018-09-12Misc. typosluz.paz
Found via `codespell -q 3 -I ../godot-word-whitelist.txt --skip="./thirdparty,*.po"`
2018-08-24Make some debug prints verbose-only, remove othersRémi Verschelde
2018-08-19Find in Files improvementsMarc Gilleron
- Search results are now grouped by file using a Tree control - You can opt out occurences when using replace mode - Double-check search results in case files have been tampered with, so occurrences don't get badly replaced - Fixed replace bug when an occurrence is found twice in one line
2018-07-26Reduce unnecessary COW on Vector by make writing explicitHein-Pieter van Braam
This commit makes operator[] on Vector const and adds a write proxy to it. From now on writes to Vectors need to happen through the .write proxy. So for instance: Vector<int> vec; vec.push_back(10); std::cout << vec[0] << std::endl; vec.write[0] = 20; Failing to use the .write proxy will cause a compilation error. In addition COWable datatypes can now embed a CowData pointer to their data. This means that String, CharString, and VMap no longer use or derive from Vector. _ALWAYS_INLINE_ and _FORCE_INLINE_ are now equivalent for debug and non-debug builds. This is a lot faster for Vector in the editor and while running tests. The reason why this difference used to exist is because force-inlined methods used to give a bad debugging experience. After extensive testing with modern compilers this is no longer the case.
2018-05-24Fix potential bugs with Find in FilesMarc Gilleron
- Iteration still going on after scan finished - Comparing milliseconds with seconds - Potential imprecision due to accumulating milliseconds (iteration could take fewer than 1ms) - Folders to scan not cleared when a new search starts
2018-05-20fixup project_manager and find_in_files for text_changed signal change.Ibrahn Sahir
Background: Commit 2abec59db96496611bb16dd1300d9b7d3def9780 removing text_changed signal emmision from LineEdit::set_text broke the project manager and find_in_files.
2018-05-01Fix Find in Files:Marc Gilleron
- FileAccess was accessed null (remains of GDScript port) - `_current_file` wasn't going up correctly in case a scanned directory had no subdirectories - Paths stored in `_files_to_scan` were not full paths
2018-02-19Added find & replace in filesMarc Gilleron