-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Remember search query" config setting does not take effect #734
Comments
I cannot reproduce this. When I set it from "ON" to "OFF", the contents of the text field are always cleared when opening the grid. |
I'll close this for now. Can you retry with your reproduction steps and report back if you can still reproduce it? |
Sure! I'll do some testing in a bit here, it's definitely possible I missed
something.
…On Sat, Dec 7, 2024, 2:24 PM Raoul ***@***.***> wrote:
I'll close this for now. Can you retry with your reproduction steps and
report back if you can still reproduce it?
—
Reply to this email directly, view it on GitHub
<#734 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIIRTR4XHMF5Z4TSYEYNBET2ENKRRAVCNFSM6AAAAABS4XGJ7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRVGMYDANZRGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I figured it out. I had it set to Two-Way JEI Synchronization, so since JEI was remembering the search query it was automatically in RS. Switched it back to one-way and it works just fine. 🤦♂️ My bad! |
No worries, thanks for reporting anyways. |
Describe the bug
The previous search term in the search bar of the crafting grid is always shown. The config value for "Remember search query" is set to "OFF" by default. Toggling it to "ON" and back to "OFF" had no effect.
How can we reproduce this bug or crash?
What Minecraft version is this happening on?
Minecraft 1.21.1
What NeoForge or Fabric version is this happening on?
NeoForge 21.1.81
What Refined Storage version is this happening on?
2.0.0-milestone.4.10
Relevant log output
The text was updated successfully, but these errors were encountered: