Skip to content
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

Search for states in tool bar #831

Open
franzlst opened this issue Apr 17, 2020 · 5 comments
Open

Search for states in tool bar #831

franzlst opened this issue Apr 17, 2020 · 5 comments

Comments

@franzlst
Copy link
Member

A text-search field in the tool bar would be useful to find a specific state dependent on its name or id.

Originally created by @sebastian-brunner ([email protected]) at 2016-01-20 06:31:45+00:00 (moved from RMC internal repository)

@franzlst
Copy link
Member Author

GTK+3 offers new widgets for searches, which could be used for that: GtkSearchEntry and GtkSearchBar

Originally created by @franzlst ([email protected]) at 2016-01-20 07:07:09+00:00 (moved from RMC internal repository)

@franzlst
Copy link
Member Author

I'm missing this feature already a while, too. I already have pressed the shortcut "strg-f" several times.

For evolving to the best solution I would recommend to locate the search-field above or below the state-machine which it is searching in. Therefore it could be a simple connection of strg-f shortcut to show the window and a close button to hide it again.
May with drop-down to select if search by id-path or name-path.

Originally created by @Rbelder at 2016-01-20 08:55:02+00:00 (moved from RMC internal repository)

@franzlst
Copy link
Member Author

How should this search bar behave? If i have three states "state_a", "state_b" and "final_state" and i type in "sta", should there be a dropdown autocompletion window? And when I select one of the results, should the state then be selected or just highlighted?

Originally created by stoertebeker23 ([email protected]) at 2016-11-11 14:41:37+00:00 (moved from RMC internal repository)

@franzlst
Copy link
Member Author

The state should be selected and the search maybe should use a focus to really be helpful, in future. So issue #37 will be really helpful to get bigger gain from this feature.

In general:
Also the in-cooperation of several check-boxes that allow to reduce search results and also search for outcomes, data ports could be helpful.

Similar it is for a global search in all open state machines if you maybe wanna search for specific library states for substitution.

For now: it seems to be enough to implement the search generally for states or ports by name and give a possibility to step through the results for the actual selected state machine.

  • so the search widget container (with a low) height can be integrated into the graphical state machine editor or state machineS editor
  • in the top is the search entry widget and next to it the option check boxes or buttons to command it
  • optional would be a list of results with a little information that can be selected and don't have to be stepped through
  • anyway the interaction with other widgets should happen by the selection and be improved later when the functionality of Some question about the built-in data and variable in RAFCON #37 is supplied

Originally created by @Rbelder at 2016-11-11 15:37:47+00:00 (moved from RMC internal repository)

@franzlst
Copy link
Member Author

I think the easiest for now is to use the State Machine tree widget. I think these list/tree widgets already offer a native search bar, if you start typing in them. Probably they need to be configured properly. Then the focus in the widget would jump to the state with the entered name (or the list would be filtered). A yet to be implemented "jump to state" feature (#37) for this widget would do the rest.

Originally created by @franzlst ([email protected]) at 2016-11-14 07:36:56+00:00 (moved from RMC internal repository)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant