-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use vl-interaction-modify with reactive features? #132
Comments
This works in a watcher, but it's a bit crude:
|
There is known bug #121, that can be related with your problem. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
ghettovoice
added a commit
that referenced
this issue
Sep 27, 2019
ghettovoice
added a commit
that referenced
this issue
Oct 3, 2019
- resolved #132 #224 #225 #226, #230 - simplified initial interaction/controls setup #95 - added `id` property for all ol components for easy identification - mixins, ol-ext and rx-ext now are build to single file package, imports from those packages are not changed - UMD version (dev/demo version) now includes all used stuff from `ol` package
ghettovoice
added a commit
that referenced
this issue
Oct 3, 2019
- resolved #173, #174, #201, #135, #216, #132 #224 #225 #226, #230 - merged of pull requests #160, #175, #180, #185, #188, #191, #206, #208, #212, #213, #215, #221, #227, #231 Thanks to @baspeeters, @sjmallon, @janlazo, @categulario, @skymaze, @jemasfox, @owen-thurston, @agmt5989, @RemiDesgrange - improved property watchers - optional debug messages - fixed broken UMD version - simplified initial interaction/controls setup #95 - added `id` property for all ol components for easy identification - mixins, ol-ext and rx-ext now are build to single file package, imports from those packages are not changed - UMD version (dev/demo version) now includes all used stuff from `ol` package - updated documentation and README
ghettovoice
added a commit
that referenced
this issue
Oct 3, 2019
- resolved #173, #174, #201, #135, #216, #132 #224 #225 #226, #230 - merged of pull requests #160, #175, #180, #185, #188, #191, #206, #208, #212, #213, #215, #221, #227, #231 Thanks to @baspeeters, @sjmallon, @janlazo, @categulario, @skymaze, @jemasfox, @owen-thurston, @agmt5989, @RemiDesgrange - improved property watchers - optional debug messages - fixed broken UMD version - simplified initial interaction/controls setup #95 - added `id` property for all ol components for easy identification - mixins, ol-ext and rx-ext now are build to single file package, imports from those packages are not changed - UMD version (dev/demo version) now includes all used stuff from `ol` package - updated documentation and README
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I create a source vector layer with features created in a template, like:
And then make the features draggable like:
vl-interaction-modify(source="waypoint-draw-target")
Then when you drag a feature, it snaps back to it's original position shortly, presumably because the source value to the feature is reactive?
So how to make existing features modifiable? If I create an empty source layer using an empty features container:
Then how to populate the features array with feature components programatically?
The text was updated successfully, but these errors were encountered: