Open Gaudon opened 10 years ago
I've written a hack to work around this by simply setting a local tag within the fragment for the last timepickerdialog that was actively shown on the screen given that only one can be present at a time. This isn't a clean or correct solution, but it will work until a fix is issued.
@Gaudon
Faced same issue today, the tag that goes in timePickerDialog.show()
is not the tag for the RadialPickerLayout thats gets passed to the callback. It's the tag for the listener which can't be accessed.
I've also implemented a solution similar to what you described, until it's fixed.
Instead of fixing the thing on your side, it could be great that you fix it for everyone. Feel free to PR ;)
I created a pull request. I tried to approach it in the most non-intrusive way, as to avoid modifying a whole lot of stuff. https://github.com/flavienlaurent/datetimepicker/pull/78
Thanks flav
Are the TimePickerDialog tags not implemented?
The above code works as .getTag() returns a string. However TimePickerDialog seems to operate differently.
In this case, the getTag() is an object and is null after calling .show() with a string tag supplied.