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

Micu/fix menu sitution 82 #83

Merged
merged 11 commits into from
May 6, 2017
Merged

Micu/fix menu sitution 82 #83

merged 11 commits into from
May 6, 2017

Conversation

micuintus
Copy link
Owner

No description provided.

We extract the functionality we added to v-play
for being able to just attach a page to the navigation
stack into its own component.

// Github issue #82
With the food and shopping menu entries in place,
on SailfishOS the menu behaves weirdly: The shopping list
gets pushed as a new page onto the stack of the food list
(without a 'PullDownMenu', which is still on the food list page).

We therefore create the entity of an 'ActionMenuItem',
which closely resembles Sailfish's PullDownMenu's 'MenuItem':
It has a 'clicked' signal, which you can connect to
for triggering some action when the menu item was clicked.

Currently, the 'ActionMenu' item uses the page component that
has been assigned to the 'initialPage' property of the
'ApplicationWindow'.

The 'NavigationMenu' abstraction on Sailfish is adapted in a
way that the menu automatically assigns itself to the first
page of Sailfish's global 'pageStack' (if it has a valid
'flickable' the 'PullDownMenu' can be attached to).
@jmastr
Copy link
Collaborator

jmastr commented Apr 20, 2017

This is just awesome! Thank you very much.

I noticed one little thing: If I put in a search term in let's say the venue list like "food" and switch over to the shopping list, the search term stays, but the list is not refreshed.

Could you refresh the list or clear the search field on switch?

@jmastr
Copy link
Collaborator

jmastr commented Apr 21, 2017

After some further investigations I noticed, that (on a v-play build) I loose the virtual keyboard after typing in "F" in the venue list and "Fo" in the shopping list. Without your patch, that does not happen. Can you reproduce that?

(avoids unnecessary indirection).
as nice as it is --- but unfortunately it is
overkill for our use case.

// Github issue #82
(vestige from debugging).
With Github issue #82 the bug of the virtual keyboard
loosing the focus was temporarily re-introduced.

// Github issue #82
for both V-Play and Sailfish: This allows us
to put the search bar in the header of the flickable
on SailfishOS, but have it as a static item on top
of the venue list on V-Play.

Closes #84
and don't implicitly use app.initialPage

// Github issue #82
Copy link
Collaborator

@jmastr jmastr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verrrrrry good work! Thank you very much!

@jmastr jmastr merged commit cf2ebed into development May 6, 2017
@micuintus micuintus deleted the micu/fixMenuSitution_82 branch May 6, 2017 13:51
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.

2 participants