note however, that if the
Surface is in a ContainerSurface that doesn't also have roundToPixel = true then the text may still be blurry
I see that this.roundTopixel is past as a parameter to _setTransform, but this.roundToPixel will be undefined because is never defined in the DOMOutput constructor, if im not wrong. https://github.com/dmvaldman/samsara/blob/1c1358047baa22610375a3dacf98a78b6ff4fcfe/samsara/dom/_DOMOutput.js#L214
thanks for the tip!
@dmvaldman
sorry for the previews incomplete comment, here is the complete one. Hello again David, i was wondering if is there a way to stop the scrolling of a scrollView that is a parent of another scrollView, I have a Parent scrollview with direction Y, and its items are scrollViews with direction X, it works when using a mouse with a mouse wheel, because the mouse wheel controls the parent view and. to scroll the child view I enable drag. but when using a trackpad or a mobile device both views scroll. so maybe it would be useful to expose a method in the scrollview to stop listening for scroll events if possible. let me know if you thinks it can be done or maybe is already possible but I just couldn’t find it.
hadn't thought about that >.<
i guess what you would want is to prevent the event from bubbling. i would think that this should happen automatically because we called
event.preventDefault. but maybe i'm missing something
okay got a fix for ya
event.stopPropagation() must also be called in addition to event.preventDefault()
lemme read into this a bit more to make sure i'm not gonna break something else ;-)
here's a (really corrupted) teaser showing some beginning work on a 3d camera
if you wanted something where horizontal dragging went to one scrollview and vertical to another, that would require something different
for that i would propose having some kind of "slider" that mapped to motion of the outer scrollview
yeah, I just test it, I dont know if it this will help. when I try it on an ipad, if I touch on a surface inside the outter scrollview, and then with the other finger, scroll the inner scrollview it works as espected, so I guees that if i can set the variable isTouching to true on the outter scrollview, it could work. or maybe is just how ios handles touch gestures, I hope you undertand what im trying to say
i could add a way to disable a scrollview
or another way: allow a way to bubble mouse/touch events that are not in the direction the scrollview is supposed to move, and capture mouse/touch events that are in the direction the scrollview is supposed to move (but this gets a little tricky)
I dont know much but yeah it seems tricky, Im just thinking how apple handles that, since a lot of apps depend on that behavior, most common one will be a List view with every item that has a swipe gesture left or right for more options. or what im trying to replacate is the appstore’s featured page.
doable though
would require a bit more work
hello. I have another question. when I set the property margins to a node or surface. it only apply it to one side and also doubles the margin number. example. if i set margins to be [10, 10], then the node is gonna have a right margin of 20 and bottom margin of 20, so my question is, is this suppose to happen and I'm just not understanding , is a bug or how do i make it behave like css margin?
so if you wanted even margins all around a Surface with a width of
10px, you'd have a margin of [10,10] and an origin of [.5,.5]
if
origin was [0,.5] then the surface would be flush on the left side, have 20px of extra space on the right, and be vertically centered (10px above and below)
since
origin defaults to [0,0] you're getting twice the margins on the right and bottom
as far as API goes, the tricky part is that I'd like setting a
margin to cause no translation. Typically a margin of [10,10,10,10] would imply reducing the width and height of a rectangle by 20px and translate it down and to the right by 10px. Unfortunately the way the code works is that "moving" and "reducing the size of" are two different code paths internally
It' seems to be 'this' is not the surface in the callback function, but the MouseInput itself. Trying to call this.setProperties({background:'blue'}); will raise an error
http://codepen.io/rockerz/pen/pEXaJW?editors=0010#0
http://codepen.io/rockerz/pen/pEXaJW?editors=0010#0
the data passed in
MouseInput doesn't have a reference to the surface you're right
it could though!