: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means waiting times in the issue tracker are very long and mostly depend on community. Sorry for the inconvenience.
State: closed new: Initial state. As long as issue is in this state, the work on the issue has not yet begun. opened: Opened state means developer started working on the issue. Feature/Fix will probably be in the next release. postponed: This means developer is not working on it now, for some reason it cannot be implemented now. Issue may be opened again in the future. upgraded: Issue is in upgraded state when developer made changes to the program and new version was released. closed: This means the user is satisfied with issue results and no more changes are needed. invalid: These issues cannot be solved. ignored: Developer decided to take no action on this issue. returned: Program changes were made but user is not satisfied and returned the issue.
> What steps will reproduce the problem?
Just a glitch. When you perform a Text Search and then select a file, the settings of the
text search are copied into the settings of the Quick Find. But when you did a Quick Find
before with another Ignore Case, the search uses the previous setting.
1) Do a Text Search with case sensitive search.
2) Open a result file.
4) Now perform a case insensitive Text Search.
5) Open a result file.
6) Do a Quick Find on the result file. The Ignore Case setting is checked, but different
casing is not matched.
> What is the expected output? What do you see instead?
The Ignore Case in the Quick Find should always reflect the setting that is used for
> What version of the product are you using? On what operating system?
> Please provide any additional information below. Attach the file you have problem with
if neccessary. If you do not want to publish files YOU CAN CHANGE VISIBILITY TO PRIVATE
megalol: The ignore case is turned on by default since a lot of time ago, right? At least
now it seems to be on by default.
koen and/or megalol: can you still reproduce the original problem? I stucked at this
point: "Open a result file", how to open it? For me it opens automatically, maybe this
changed earlier in the past year.
No, it is still present in 6.0.2 build 915.
First search for "frame" case sensitive (using the "Text Search" tool). Then open a file
from the results list (search2.gif).
Then search for "Frame" case insensitive. (search1.gif)
Select a found file (search2.gif)
As you see in search3.gif, The local search is now set to "Frame" and ignore case. But
when using the arrow down button, it won't find "frame" on line 14.
Please try the latest nightly, it should be fixed.
I can't edit the attachments, but i changes this issue to developery only until JPEXS
removes the paths or the complete images (i don't need them anymore.)