Printable View
Please see attached example (Designer Pro X file).
Xara's navigation bar leaves the mouseover state active when the user jumps to a web page. I would rather that the active page button NOT be highlighted. I can't see any applicable option in the Edit Navigation Bar dialog for overriding this. Might anyone know how this can be done? Thanks.
If you want to disable automatic highlighting of the link to current page, add the "NoAutoHighlight" name to the object.
http://www.talkgraphics.com/showthre...anced-features
hih :thx
Thanks for your kind reply.
Covoxer said:
"6. If you want to disable automatic highlighting of the link to current page, add the "NoAutoHighlight" name to the object."
I located the target button in the Page & Layer Gallery (a "Repeating Group"), right-mouse clicked, selected "Names," then applied the name NoAutoHighlight. That's not working as I hoped. How else might I "add the NoAutoHighlight name to the object"? Perhaps you could use the attached .xar file in my opening post to clarify. Thanks a million for your assistance.
Confirmed here.
Why thank you, Mr. Moderator Emeritus Dude, Sir. =)
Curtis, you are using the wrong document type for a website.
Sledger - I tried creating a new website with five pages and using a navigation bar from the Page Elements folder.
I selected the nav bar and applied the name with the quotes.
I still get a highlighted button on each page.
The NoAutoHighlight only works in web documents and only works with single buttons.
Convert the doc type to web document then un group the navbar buttons and apply the NoAutoHighlight name to each button on each page.
Once they are a group in a navbar, the function doesn't work.Quote:
Originally Posted by gwpriester
you may be able to get it to work if you add a MouseDown layer
iirc with NoAutoHighlight the MouseDown is displayed instead of the MouseOver obviously only if MouseDown exists
The MouseDown automatically becomes the highlighted page button state Frank. I use this all the time to have the highlighted page button different from the mouse over button.
Thanks a bunch, guys. It's a shame that Xara doesn't provide the option to apply the NoAutoHighlight to the full navbar (within the Edit Navigation Bar dialog).
exactly my pountQuote:
Originally Posted by gwpriester
he wasnt using onmousedown before so if the onmousedown state is the same as mouseoff then thats sorted his problem
i think
:thx
In order to use a mousedown state/layer one couldn't use a Xara navigation bar object. As far as I can tell, navbar elements only use mouseoff and mouseover layers.
bah, i never use xara navbars
and there youve just given me yet another reason not to
you can create marvelous unique and individial menu styles
as long as you stay away from that archaic navbar feature!
i did this menu by hand, so much easier than fighting with the stupidnavbar thing
work in progress for new client so ignore the fact most things don't work
http://beretgascon.com/ccpt/
go to découvrir > où manger > fermes auberge to see menu at work
its done by hand and wasnt difficult and didnt give me a headache
:thx
Nice navigation system, Béret.
Before Xara introduced navigation bars as objects that are controlled with a pop-up dialog, one had to create a multitude of layers and companion pop-up layers. In 2008 I created a lengthy text tutorial on how it's done, then followed up with an instruction video. The two are referenced within the same thread/topic. They can be accessed by clicking the pair of links in my signature. Since you don't use Xara navbar objects, Béret, I would be curious to know if there is a less cumbersome system for creating smart navigation bars using Xara software. Thanks. =)
Curtis - Create your button with the three states first and Apply Soft Group. Then create your nav bar. It works (preview attached).
Thanks a million, Gary! =)
The MouseDown option doesn't allow the type of visual feedback that I want. It looks like the only way to get what I want is to follow Steve's method from post #8 in this thread. Thanks again for all your help and advice.
I was dreading having to apply the NoAutoHighLight name to all the MouseOff and MouseOver objects (on every page). As it turns out, they can all be conveniently group-named.
- navigate to a page that has the navbar that you want to modify.
- mouse-select the navbar.
- hit Ctrl+C to copy the navbar to the clipboard.
- hit the Delete key.
- click Delete from all pages.
- hit Shift+Ctrl+V (paste in place).
- make sure that the Page & Layer Gallery is open.
- expand the MouseOver and MouseOff layers to display their objects.
- on the web page, double-click the Xara navigation bar object to edit it.
- click the Ungroup to edit graphics button (lower left).
- note that all affected objects in the Page & Layer Gallery are highlighted.
- with all items highlighted/selected, Arrange > Apply Soft Group.
- right-mouse click within either of the two highlighted groups in the Page & Layer Gallery, then click Names... from the pop-up menu.
- in the Apply name edit box type NoAutoHighLight, then click the Add button.
- right-mouse click the object group and click Repeat on all pages.
- delete any unwanted softgrouped set of buttons from any page where it doesn't belong.
Shift+Ctrl+V (paste in place).
Thanks for the correction, Steve. I've modified the post accordingly. :cool:
Cursor - just out of curiosity...
Why do you not want the current page highlighted? Are you indicated current location on the site in some other way?
In building HTML pages, one of the things that makes a "template" master page a pain is that you kind of have to leave the navigation out of the template part of the file so that you can apply a special class independently for each page to allow for the special "current" styling, so I thought (especially for someone building complete sites in Xara and not just mockups) that this feature would be really useful, and if not, then that person would probably want to build their nav bar completely from scratch anyway (like we used to have to do in the original days of Xara web designer - pre-navbar-existence.
Again, just curious about the thought process.