Hey all, I'm confused as to why TileService events...
# compose-wear
a
Hey all, I'm confused as to why TileService events are protected. Specifically onTileAddEvent, onTileRemoveEvent, etc. I'm extending the CoroutinesTileService, and now I don't have access to those events for my analytics :( was this done on purpose to hide those events ?
a
No, it wasn't done on purpose. @yschimke is this something to with CoroutinesTileService not explicitly redeclaring these functions as open? 🤔
@Arjun Achatz Please could you open an issue on the Horologist repository?
a
Yeup I just did that !
This is on latest version, maybe it was before?
If it's on an older version, I can fix on the release branch 0.2.x and release in a couple of days.
a
, I tried to reproduce the behavior but was unable (I can override onTileEnter etc).
This is on latest version, maybe it was before?
Arjun is on an older version - CoroutineTileService is now called SuspendingTileService
a
Kk I just pulled 0.4.1 and you guys are right 🙏
I also closed the issue
Thanks for the quick responses!
y
Does that work for you? It's wear compose 1.2 alphas. If so, great!
a
For the tiles artifact?
y
No, but tiles alphas.
Good catch
a
oh cool, I haven't tried these yet 🥲
a
I haven't tried running it yet, but will try and post results here
y
I can't see where they were ever hidden. They are protected by the Androidx Tiles library, but that's fine for subclasses to implement.