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

[kirigami] DatePicker dialog doesn't pop() when accepted #380

Merged
merged 2 commits into from
Nov 22, 2024

Conversation

jmlich
Copy link
Contributor

@jmlich jmlich commented May 17, 2024

In c48f79b there was a fix of Dialog behaviour for Device Unpair operation. This broke DatePicker Dialog (User Settings -> Birthday) .

In this fix is used acceptDestination variable show the Unpair works with previous implementation and DatePicker works as well.

Same issue applies to TimePicker Dialog as well.

The change may affect also unpair page

@jmlich jmlich marked this pull request as draft May 17, 2024 09:13
@jmlich jmlich force-pushed the dialog-via-acceptdestination branch 2 times, most recently from 1ca6805 to cff87a7 Compare May 17, 2024 09:20
@jmlich jmlich changed the title [kirigami] Dialog pop should be done via accept destination [kirigami] DatePicker dialog doesn't pop() when accepted May 17, 2024
@jmlich jmlich force-pushed the dialog-via-acceptdestination branch from cff87a7 to cc6deb5 Compare June 3, 2024 06:34
@piggz
Copy link
Owner

piggz commented Oct 24, 2024

is this still wip?

@jmlich
Copy link
Contributor Author

jmlich commented Oct 24, 2024

Yes, there are at least two cases with use of that mechanism which are bound together. I not sure exactly, therefore mentioning following three (maybe I have missed something):

  • SettingsProfile -> Birthday (DatePickerDialogPL) -> Save()
  • FirstPage -> PairSelectDeviceType -> PairPage -> FirstPage
# to avoid UnPairDialog is necessary to remove old settings manually.
[defaultuser@PinePhone ~]$ dconf list /uk/co/piggz/amazfish/
[defaultuser@PinePhone ~]$ dconf reset /uk/co/piggz/amazfish/pairedName
[defaultuser@PinePhone ~]$ dconf reset /uk/co/piggz/amazfish/pairedAddress
rm -f ~/.config/harbour-amazfish/harbour-amazfish.conf
  • FirstPage -> UnpairDeviceDialog -> PairSelectDeviceType -> PairPage -> FirstPage (UnpairDeviceDialog must not appear)

I have seen some suspicious behavior with UnPairDialog, where it should replace dialog or pass it with attachedpage mechanism, but it was somehow unreliable. I have seen overlapped FirstPage in background in SailfishOS.

I have spent some time with that already without reasonable result.

@jmlich jmlich force-pushed the dialog-via-acceptdestination branch from d8d3232 to 2d1aff4 Compare November 22, 2024 12:23
@jmlich
Copy link
Contributor Author

jmlich commented Nov 22, 2024

Works on SailfishOS and Kirigami, but on Ubuntu Touch is following error when clicked to unpair:

Nov 22 15:22:46 ubuntu-phablet aa-exec[3723]: file:///opt/click.ubuntu.com/uk.co.piggz.amazfish/2.4.0/share/harbour-amazfish-ui/qml/components/platform/DialogPL.qml:44: TypeError: Property 'push' of object ApplicationWindowPL_QMLTYPE_3_QML_42(0x62970b2840) is not a function

@jmlich jmlich marked this pull request as ready for review November 22, 2024 16:19
@jmlich
Copy link
Contributor Author

jmlich commented Nov 22, 2024

It looks like everything works now on all platforms. I am wondering if there were another scenario which I didn't considered or forgot.

@piggz piggz merged commit dbd7a48 into piggz:master Nov 22, 2024
4 checks passed
@jmlich jmlich deleted the dialog-via-acceptdestination branch November 23, 2024 06:26
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