# ScrollViewMotion, compilation explodes with Observables

**URL:** <https://forums.fusetools.com/t/scrollviewmotion-compilation-explodes-with-observables/3026>\
**Category:** Bug Reports\
**Created:** [September 3, 2016, 9:20pm UTC](https://forums.fusetools.com/t/scrollviewmotion-compilation-explodes-with-observables/3026 "2016-09-03T21:20:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sebastian](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/sebastian/32/594_2.png) [@sebastian](https://forums.fusetools.com/u/sebastian)\
**Post date:** [September 3, 2016, 9:20pm UTC](https://forums.fusetools.com/t/scrollviewmotion-compilation-explodes-with-observables/3026/1 "2016-09-03T21:20:38Z")

</div>

When trying to use observables to configure ScrollViewMotion, compile explodes.

```auto
<JavaScript>
exports.gotoDuration = Observable(0.1)
exports.gotoType = Observable('SmoothSnap')
</JavaScript>

<ScrollView ux:Name="view">
  <ScrollViewMotion GotoDuration="{gotoDuration}" GotoType="{gotoType}" />
</ScrollView>

```

Error:

```auto
Fuse 0.25.0 (build 7511)
Build started: FullCompile
Configuring (5.16s)
Compiling syntax tree
build/Local/Preview/cache/ux11/Veckoappen.unoproj.g.uno(32.66): E2047: No implicit cast from Fuse.Motion.ScrollViewMotion to Uno.UX.PropertyObject
/Users/jhsware/Fuse/Veckoappen/build/Local/Preview/cache/ux11/Veckoappen.unoproj.g.uno(32,67,32,73): Error E2047: No implicit cast from Fuse.Motion.ScrollViewMotion to Uno.UX.PropertyObject
build/Local/Preview/cache/ux11/Veckoappen.unoproj.g.uno(41.66): E2047: No implicit cast from Fuse.Motion.ScrollViewMotion to Uno.UX.PropertyObject
/Users/jhsware/Fuse/Veckoappen/build/Local/Preview/cache/ux11/Veckoappen.unoproj.g.uno(41,67,41,73): Error E2047: No implicit cast from Fuse.Motion.ScrollViewMotion to Uno.UX.PropertyObject
(1.92s)

Build completed in 7.10 seconds
    2 errors
Build ended
fuse: Failed to compile project

```

---

<div class="post-metadata">

**Author:** ![BeeWarloc](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/beewarloc/32/186_2.png) [@BeeWarloc](https://forums.fusetools.com/u/BeeWarloc)\
**Post date:** [October 26, 2016, 1:40pm UTC](https://forums.fusetools.com/t/scrollviewmotion-compilation-explodes-with-observables/3026/2 "2016-10-26T13:40:53Z")

</div>

Hi, thanks for the bug report. And sorry for the slow reply.

Unfortunately the properties on ScrollViewMotion does not currently support binding, and I’m not sure exactly if and when that will happen. If this is a serious limitation for you then tell us your usecase, and we might be able to help you with a workaround. 🙂

I also think the error message you’re getting is rather confusing, and I’ll create a ticket for improving that.

---

<div class="post-metadata">

**Author:** ![sebastian](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/sebastian/32/594_2.png) [@sebastian](https://forums.fusetools.com/u/sebastian)\
**Post date:** [October 26, 2016, 2:13pm UTC](https://forums.fusetools.com/t/scrollviewmotion-compilation-explodes-with-observables/3026/3 "2016-10-26T14:13:42Z")

</div>

Hi! Thanks, I found a solution for my use case using the existing API.

---

<div class="post-metadata">

**Author:** ![dalibor.ilic.dado](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/dalibor.ilic.dado/32/209_2.png) [@dalibor.ilic.dado](https://forums.fusetools.com/u/dalibor.ilic.dado)\
**Post date:** [January 31, 2017, 7:29am UTC](https://forums.fusetools.com/t/scrollviewmotion-compilation-explodes-with-observables/3026/4 "2017-01-31T07:29:16Z")

</div>

And the solution was?

---

<div class="post-metadata">

**Author:** ![sebastian](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/sebastian/32/594_2.png) [@sebastian](https://forums.fusetools.com/u/sebastian)\
**Post date:** [January 31, 2017, 10:33am UTC](https://forums.fusetools.com/t/scrollviewmotion-compilation-explodes-with-observables/3026/5 "2017-01-31T10:33:40Z")

</div>

I used .seek, it wasn’t the perfect solution because it jumps to the target position but scrolling would have been too slow in my case anyway.