I’ve been attempting to make horizontal and vertical side areas (like many people do), but keep the blank corner…
I’ve been attempting to make horizontal and vertical side areas (like many people do), but keep the blank corner space inaccessible with the new Stop Points. I can’t get it to work. Any suggestions?
Also, if you notice in my screenshot, I use a pretty tight grid, which means my Stop Points get cropped. This is a bit ugly and can make it difficult to see Directions at a glance.
Oh, and while speaking of Stop Points, the word Direction in the Stop Point Configuration screen confuses me every time. Perhaps Swipe Direction would be a bit clearer.
]]>« Open Folder Action… (Previous Post)
(Next Post) I know this has been mentioned before, and Pierre Hébert said it would be ‘complex to configure’, but I think… »
D5 Creation
< ![CDATA[
Try to also check ‘barrel’.
How can you put it in the middle of the layout? Are you in free mode?
]]>
< ![CDATA[
Setting Barrier would be what I want, if the Stop Point worked correctly, which it currently doesn’t. When in the position it is in the screenshot, it doesn’t do anything. When moved one position right, it stops scrolling halfway (as expected).
Although I normally use grid mode, I’ve switched to free mode and experimented. When I zoom in extremely close and move the stop point very precisely, I find that there’s a threshold where the Stop Point works (it’s when the glow from the back of the arrow’s head just touches the page line). At that placement there is one pixel of scrolling motion before the Stop Point registers.
Here’s the thing: in grid mode, we’re one pixel outside that threshold.
]]>
< ![CDATA[
Uhm…it’s true. But if you uncheck ‘snap to pages’ in the settings config it work (more or less)
]]>
< ![CDATA[
All of my tests were done with ‘Snap to pages’ disabled. I’ve now tried every combination of ‘Snap to pages’ and ‘Fit desktop to items’ with no success 🙁
]]>
< ![CDATA[
Michael, this is the same issue I am having with stop points. My understanding, and Pierre Hébert correct me if I’m wrong here, is that stop points don’t “activate” until they appear on screen – thus their affect wouldn’t be felt until they appeared on screen. If you put them on the screen’s edges in snap mode, then they are technically off screen. I’ve done very similar experiments in and out of free mode and I think this is what is causing a similar issue in my design. I’m trying to achieve the same effect.
]]>
< ![CDATA[
Jacob Nyhart Hm, did you mean to say that when Stop Points are on a page edge, they are technically ON the page / screen (from both directions), and thus will not activate until they move (or are about to move) off screen? Because that’s what my experiments are leading me to believe.
This seems like a bug. Expected behavior (in my mind) would be that they activate on swipe before motion begins. So if I’m making sense, Stop Points on page edges should be OFF screen.
]]>
< ![CDATA[
Honestly, I don’t have a complete understanding on how the stop points work now… I’ve tagged Pierre Hébert a few times now in the hopes he responds and can point me in the direction of some sort of demonstrative video tutorial. 🙂
]]>
< ![CDATA[
i pin th top and bottom items horizontal only to avoid these blank corners.
i think setting desktop wide makes them active when not onscreen.
]]>
< ![CDATA[
Klyntone Bourserk Pinning horizontally (or vertically) makes sense for avoiding those corners, but only if you’re using full pages (not ‘Fit desktop to items’ and ‘Snap to pages’). Otherwise, it has some not so good side effects.
Normally a stop point is activated when it enters or exits the current view / screen (I believe). So yeah, desktop wide creates conceptual stop lines across the entire desktop. This also doesn’t help my circumstance unfortunately.
]]>
< ![CDATA[
I think there is a problem with barrier as they are today, but it’s more a functional problem than a bug. I still need to find a workaround yet !
]]>
< ![CDATA[
nooooooo… th barriers are working really well for me 😉
]]>
< ![CDATA[
yes but there are use cases where they are not good enough. For instance using two SP barriers on each side on the page in grid mode won’t work. This is especially annoying for the maze template I am working on !
]]>
< ![CDATA[
The latest beta improves SP handling and fixes bugs, including barriers. I just post a short tutorial on how to isolate a corner 🙂 https://plus.google.com/u/0/112252356715774925798/posts/EBfDM3woTYp
]]>
< ![CDATA[
Thank you so much! I was isolated from the Internet this weekend. Now I’m back and I’m astonished and thrilled by the progress 🙂
]]>