Yup, confirmed, in the metadatas, longitude depends on
x. But using the main property center.x isn't working quite right either. Its actually returning the same as longitude, even though in the browser console I have a global set to view that returns a different coordinate system value
I'll keep fiddling with it, you've gotten me to a good point where I think its close. Thanks much for the help!
:100:
I did this trick to force redrawing of charts in a pre-can-reflect project.
(of course, that only works if center.x is never zero)
Dropping another symbol on the object as a handler store should suffice. So:
Not sure if you're familiar with dojo, but can I just decorate the Accessor class perhaps?
(jk)
:D
but there is a known bug with nested setTimeout Functions
that for example blocks socket.io from working correctly with zones
if you want to know more about the logging in canJS
that is a t present part of can-util/dev/dev
that is depricated and now
can-log/dev/dev :)
but to make it more short done-autorender which uses zones has a option called no-zone
which bypasses zones complet :)
@bmomberger-bitovi So I'm working on this can symbol observability stuff again today, and I'm back at a point where I'm not sure what's wrong. I've found out that the
watch function doesn't always work, when working with nested objects, so to workaround that, I've modified my function to use .watch('center.longitude'...) which does work. The template renders the initial value, but the template still isn't getting updated when the values change. My onKeyValue handler is getting called. But my getKeyValue is not getting called after that which is where I believe the problem lies.
Here's the whole gist https://gist.github.com/roemhildtg/8a52e5e710280ad6e9d01483d1e695d6
sorry, maybe that makes sense
so you're saying
onKeyValue is called, then whatever triggers watch happens, and your handlers don't update the template?
getKeyValue shouldn't have to be called after that in order for it to work
I think I have it working pretty much like I have in my dev setup
I don't know that this is the root of the live problem, but it couldn't hurt to clean that up.
Oh! I do see one thing that might be a problem with your @@can.getKeyValue. It's using can-util/js/get/get, which doesn't use canReflect.getKeyValue to access properties.