I created a rollover out of three images: one for the normal state, one for the mouseover and another for the click state. i set the parameters for mouseover and click to “items”. however, the click image only appears in the page preview in Freeway. when i preview the page in a browser the click state does not appear.
any ideas?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
here’s a good tutorial movie, follow the steps in this:
http://freewaycast.com/screencasts/view/49-rollovers-in-freeway-5
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
jimmy,
thanks for the tip but the tutorial only deals with with the normal and mouseover states.
so i am still looking for answers. thanks anyway.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Sometime around 22/1/10 (at 08:36 -0500) Edson Mahfuz said:
the click image only appears in the page preview in Freeway. when i
preview the page in a browser the click state does not appear.
The Click state is shown once the user has clicked a rollover.
However, if that rollover is also a link to a different page then the
user goes to the new page rather than hanging around to see the
change in rollover state.
Freeway’s internal Preview display is a single page thing - links to
other pages don’t take you to the other pages. This is useful as a
way to preview a single page quickly, without having to wait for all
other modified pages to be rebuilt. If you need to test actual
navigation then you’ll need to preview in a browser instead.
If you want to simulate the click state in the destination page then
you’ll have to set up the appearance of the relevant link item there,
so that its normal and/or rollover state matches the intended click
state from the previous page.
I’m afraid this is normal stuff in web page design; without funky
scripting to work around this, each page is a self-contained entity
that answers to no other.
k
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
thanks, keith. very informative reply indeed. i will try your suggestion for sure. regards.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Sorry, but adding a link to a different page does NOT in fact show the Rollover CLICK state. If it does show, my computer must be too fast to show it. The CLICK state needs to show immediately on MouseDown and remain visible until the mouse button is lifted. That is how any proper CLICK state works. Try it yourself in OS X. Hover over any of the 3 stoplight buttons in the upper left of a window, then click and hold. Note the CLICK state. That is what we all want the Rollover CLICK state to do.
James Wages
freewaytalk mailing list
email@hidden
Update your subscriptions at:
A click is actually a compound event. It occurs when a mousedown and mouseup have happened within the screen bounds of the listening object. You can see this in Mac OS if you click the mouse button down on a button, then slide the cursor off of the button and release the mouse after the cursor is outside the bounds of the button. The effect will be as if you did not click the button at all, or tried to and missed it.
The “click” visual state that you are referring to is actually the mousedown state. It cannot be triggered by a click handler, because the click doesn’t fire until after the button has been released and mouseup has fired.
The Rollover Action creates handlers for either the mouseover/mouseout events or the click event. As far as I know, it does not handle the mousedown/mouseup pair directly. There is no un-click event to handle resetting things, because click fires after the mouseup, not before. So the only possible visual feedback would be click (mouse released) and stick (visually) until something else is clicked.
If you are using this Action on a link to a new page, there’s another wrinkle here. In Safari at least, once you have followed a navigation link or submitted a form, no further updates to the DOM are visually painted to the screen. So even if the class or style attributes are manipulated in a click event, for the entire time that it takes between the request and screen repainting with the new destination page, the previous page is sitting there frozen, with no updates shown to the visitor. You can watch the page in the Web Inspector, and see your updates happen to the HTML/DOM, but you won’t see any visual indication that they have changed. I see this all the time when I have a form button set to disable once clicked. In every other browser, the button will turn gray and lose its “clickability”, but Safari will resolutely show the appearance of the button in its last state, even though it is disabled, and clicking it twice does not work.
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Walter, although I appreciate your detailed explanation, the fact remains that…
There is not CLICK state displayed at all, neither on MouseUp nor on MouseDown.
That remains true regardless of the link being to content on the same page or a link to a new page.
The current functionality is therefore TOTALLY AND UTTERLY BROKEN, and therefore it ought to either be (a) deleted from Freeway or (b) fixed. We all would prefer the latter.
Hence my previous post.
Hopefully the fix will come quickly. For truly: Never defer to tomorrow what can and should be done today! 
–James Wages
freewaytalk mailing list
email@hidden
Update your subscriptions at:
This is a very quick example that uses the standard Rollover action on the Penguin image.
Normal, hover and click states have been set. I have applied a dummy link to the image so you dont leave the page before seeing the Click state.
http://deltadesign.co/FW7Test/simplerollover.html
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Great. I am pleased to see YOU were able to get the CLICK state to work. But I now want to know how to transfer your magic trick to my sites, where the CLICK state NEVER works.
For example (this is just one of many), open this page in my site…
http://www.visionsecurity.jp/jp/buy.html
Click any of the clickable prefectures in Japan.
You will see popover content display, and there will be a little “X” mark close box in the upper right. I used Rollover action 2.12 in Freeway Pro 7.1.1 to apply Normal, Mouseover, and Click states to that close box, as shown in the following screenshot:
http://cl.ly/2j2I3r0P1e2d/Image%202016-01-07%20at%208.52.34%20AM.png
Now click that close box. You will find that Normal and Mouseover (hover) states work great, but the CLICK state never displays.
And here is a screenshot showing what each of the 3 linked states looks like:
http://cl.ly/1d3C1b2Z3H2L/Image%202016-01-07%20at%208.56.29%20AM.png
And there you have it.
–James Wages
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Same version of the action and I do it this way http://www.deltadesign.co/fw_examples/fwactions/rollover.html
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
That is precisely how I always do it too. And here’s a screen shot of the PARAMETERS tab for you too:
http://cl.ly/2I3c2w383E3h/Image%202016-01-07%20at%2010.37.45%20AM.png
But let it be known that I have tried to get CLICK to work for YEARS, and it never works for me. EVER.
Note that I am linking to content on the same page. I am not using links on those rollovers to external content, if that matters. But it shouldn’t matter. I am also using pass-thru images, if that matters. But that too should not matter. Furthermore I am using the high-resolution setting, but even when I don’t use that setting the CLICK state never displays.
And if someone in this thread comes along and shows me another stripped-down Freeway document where CLICK works, the fact remains it does NOT work for me. Perhaps someone could take a look at the HTML on my example page and use that to explain WHY the CLICK state (for the close boxes) never displays AND how it can be fixed:
http://www.visionsecurity.jp/jp/buy.html
–James Wages
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Once again, I’ve stumped the masters!
Well, to spur this discussion onward, here is a code snippet from the page I twice linked for everyone previously…
<a href="#" onmouseover="FWRestore(1,'Zinc');FWSRestore(top.frames,'Zinc');FWLSwap('CloseBoxNRM10',1,'CloseBoxROL-144.gif','CloseBoxNRM10','Zinc')" onmouseout="FWRestore(1,'Zinc');FWSRestore(top.frames,'Zinc')" onclick="setTimeout('FWRestore(2,'Zinc');FWSlave(top.frames,'Zinc',10,2);FWLSwap('CloseBoxNRM10',2,'CloseBoxCLK-144.gif','CloseBoxNRM10','Zinc',10)',0)"><img id="CloseBoxNRM10" src="CloseBoxNRM-144.gif" alt="閉じる" title=""></a>Once again, the example page from which I pulled the above code is found here:
http://www.visionsecurity.jp/jp/buy.html
The “CloseBox” is the one on which I am using 3 rollover states, including the CLICK state. And the CLICK version graphic has CLK in its name, as shown in the code above.
But as I said before, that CLICK state never shows. No doubt you visited my web page above and discovered the same, no?
So the question at this point is, why, on an HTML level, is the CLICK state NOT showing? Once we know that, we then know how to fix the problem in Freeway, seeing that the Rollover action is responsible for generating the above code.
Thanks,
James Wages
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Ditto my previous post.
I take it from the lack of replies that:
My life won’t end without the CLICK state, but the fact it is BROKEN remains. The first step toward FIXING that problem is to admit the problem exists. And of course, it helps if someone other than myself can verify that same problem. Just showing me an example of where it works does not say there is no problem, as evidenced by the fact I’ve already proven beyond any doubt the problem exists.
Again see my previous post for details.
Thanks.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
James - the problem here is more of engagement.
Speaking for myself I am having trouble relating to your problem because I a not really sure how you want your example page to work.
If I understood Japanese I guess that would help and then rather than offer to ‘Fix’ an action that works for me I would try to offer a solution to your specific need.
But for me it is more about investing time that is in short supply to help the most amount of users. And in this case there don’t seem to be many users crying out for this.
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Dave, thanks for your continued replies.
Most people stop crying (or never cry to begin with) when they see it’s a lost cause. They don’t complain because they simply gave up. I, on the other hand, am a persistent thorn-in-the-flesh until I see progress on a particular issue, hence my endless posts in this thread. Sometimes that persistence really pisses folks off. Other times, it provokes a solution. Not knowing which will occur, I persevere in hopes of finding that solution, knowing that it will be for everyone, not merely for myself alone.
The fact there is Japanese on my example page is irrelevant to the problem at hand. In fact, the map itself is irrelevant. I merely posted that page because I have Normal, Hover and Click states applied to each of the clickable prefectures (states) on that map.
Here is that page again:
http://www.visionsecurity.jp/jp/buy.html
Don’t worry about Japanese. Just open the page and hover your mouse over the map in various spots. When you see a hover (rollover), then click. Take note you do not see the CLICK state. That’s the entire problem.
Thanks,
James Wages
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Please make a static mockup of how it should look in each of the three states, side-by-side. I have resisted the urge to look into this because it appeared to work when I clicked on it – an overlay appeared, covering the place I had clicked, so there was no way to see how the button on the map should have looked while it was in the clicked state. As I have explained previously, the click “state” is a compound state. There is no inverse of click, because it is a terminal state. Unlike mouseover, which has an equal-and-opposite mouseout to “cancel” it, there is nothing to cancel a click, except another click on another object. This means that if you do something with a click, you have to declare how you want to step out of that clicked state. The Action does not offer anything except a (color name) channel and a click index as far as an interface to declare this intent.
Walter
On Jan 12, 2016, at 3:08 AM, JDW email@hidden wrote:
Don’t worry about Japanese. Just open the page and hover your mouse over the map in various spots. When you see a hover (rollover), then click. Take note you do not see the CLICK state. That’s the entire problem.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options
When you see a hover (rollover), then click. Take note you do not see the CLICK state.
I hear what you are saying but it would help my understanding if I knew what your click state was meant to signify.
However I did post a reply to another thread yesterday that used Target Show/Hide along with the Rollover action to create a similar effect but I would consider it too cramped a layout to use on your page - making it properly responsive would be tricky too.
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options
My apologies for explaining it wrong. It is actually the “Closebox” in the upper right corner of the overlay content that has the Hover and Click states, not the prefectures. Sorry for that instructional mistake.
Separately from that, I created a simplified page with just the Closebox, explaining the matter in detail, with both an internal link and an external link:
http://kiramek.com/click-state-test/
The CLICK state does not appear on MouseDown. It displays only on MouseUp. But if you are linking to something outside the page itself then your computer will probably be too fast to display the CLICK state, making it impossible to use a CLICK state for a Closebox. That is the problem.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
As I have been taking pains to explain to you, that’s because the click event never fires until the mouseup is over. Mousedown + mouseup = click. Freeway can’t change that. JavaScript can’t change that. That’s what the W3C decided that a click would be.
In JavaScript (as in hand-written JavaScript) you can observe the mousedown event, which is not the click event, and cause it to respond in any way that taste allows. If the Rollover Actions was extended to include an observer for the mousedown event, then you could use that to write that as well. But then you would also have to observe the mouseup event, and possibly the mouseout, too, and remove whatever effect you applied on mousedown, because otherwise someone could mouse down on the button, and then slide the cursor away from the button, leaving it stuck that way.
Walter
On Jan 12, 2016, at 9:24 PM, JDW email@hidden wrote:
The CLICK state does not appear on MouseDown. It displays only on MouseUp. But if you are linking to something outside the page itself then your computer will probably be too fast to display the CLICK state, making it impossible to use a CLICK state for a Closebox. That is the problem.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options