Hi, My preferred solution for this issue is calling `om/value' on the cursor before passing it to non-ui parts of the application. You can also move that call into the functions that get called itself, as it's equal to the identitty-functions for non-cursors.
The other (more hacky) solution is extending MapCursors etd. to the protocols you need & wrap every function of those with `om/value'. This has the benefit of being non-visible when using cursor, but has the drawbacks of braking `satisfies?' etc. tal giat writes: > How can I have an om cursor implement a protocol and then call that protocol > method from an om component ? the problem is that I'm getting an error > calling the protocol method because the type now is not the given type but > om.core/MapCursor. -- Moritz Ulrich
pgpUekvJc6kWM.pgp
Description: PGP signature
