-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add Find / Find Next support to the Public Talks database #118
Comments
Relates to #102 |
I have made a start on this and added support for:
|
I have now added support for:
But, there are some scenarios to keep in mind:
|
The above issue has been addressed. |
@cengizu
Sure, but that introduces some new concepts:
I might implement it at some point. We'll see!
Well spotted. I forgot to add CTRL + F to the accelerator table. Now it should function as expected.
I'll remove the menu button if / when I implement the extra buttons on the Find window.
I am not getting any crashes, but it might be because I added the accelerator hotkey. I am sending you a beta and would like you to try it. |
I asked ChatGPT what code changes would be needed to support bidirectional searching. It should be doable, if the proposed adjustments are sound! 😊 We won't know unless we try. But bidirectional searching in the congregation database will be harder. Also, another thing we must keep in mind is that we must move the Find window to ensure the focused control is visible. |
Is your feature request related to a problem? Please describe.
The Public Talks maintenance page in PTS includes a Find / Find Next feature (refer to the screenshot in the Additional Content section below).
In PTS, the search functionality is restricted to:
It would be beneficial to incorporate a Find / Find Next feature into the Public Talk Manager in MSA.
Describe the solution you'd like
MSA would have a broader search scope:
This feature could be expanded to include additional fields from the history, such as:
Additional context
Here is where Find / Find Next is located on the Public Talks maintenance page in PTS:
The text was updated successfully, but these errors were encountered: