Skip to content

Conversation

@michaelgregorius
Copy link
Contributor

Move the search bar on top of the file browser for the following sidebar windows:

  • "My Projects"
  • "My Samples"
  • "My Presets"
  • "My Home"
  • "My Computer"

Also rename some variable names to something more meaningful. Rename the member m_l of FileBrowser to m_fileBrowserTreeWidget. Rename the following local variables in the constructor of FileBrowser:

  • ops -> searchWidget
  • opl -> searchWidgetLayout

@WrillicR
Copy link
Member

@michaelgregorius thanks! Glad to see you doing this!

@PhysSong
Copy link
Member

@michaelgregorius Why the target is master, not stable-1.2?

@BaraMGB
Copy link
Contributor

BaraMGB commented Jun 25, 2017

Why the target is master, not stable-1.2?

Because this is not a bug fix.

@PhysSong
Copy link
Member

Okay.

…S#3657)

Move the search bar on top of the file browser for the following sidebar
windows:
* "My Projects"
* "My Samples"
* "My Presets"
* "My Home"
* "My Computer"

Add the greyed out text "Search" to the search text edit.
The text is only shown as long as no text is entered in the search field.

Also rename some variable names to something more meaningful. Rename the
member m_l of FileBrowser to m_fileBrowserTreeWidget. Rename the
following local variables in the constructor of FileBrowser:
* ops -> searchWidget
* opl -> searchWidgetLayout
@michaelgregorius michaelgregorius merged commit 1b24a05 into LMMS:master Jul 7, 2017
@michaelgregorius
Copy link
Contributor Author

I have merged regardless of the failed builds as they seem to have been caused by problems with fetching the necessary packages for the build as can be seen here.

The Linux build has built successfully on my machine and the changes were very limited, therefore I assume that everything is OK.

By the way, is it possible to manually trigger another build without making any changes to the branch?

@michaelgregorius michaelgregorius deleted the 3657-MoveSearchBar branch July 7, 2017 16:55
@tresf
Copy link
Member

tresf commented Jul 7, 2017

By the way, is it possible to manually trigger another build without making any changes to the branch?

Yes, for some of us at least... just click the Restart Job button.

@michaelgregorius
Copy link
Contributor Author

@tresf Thanks for the tip! I have checked with the old builds and it's not enabled for me.

@tresf
Copy link
Member

tresf commented Jul 10, 2017

I have checked with the old builds and it's not enabled for me.

It should at least be visible for your own PRs, but I just looked at GitHub security and you're not in the admin group, you're in the developers group, Travis-CI must require project admin, I can't find a setting to override this. We can change access upon request, but that should be done offline.

@michaelgregorius
Copy link
Contributor Author

@tresf No need to change something. I guess we don't need to restart a build that often and in case it is needed urgently I will contact you.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants