News:

BB code in posts seems to be working again!
I haven't turned on every single tag, so please let me know if there are any that are used/needed but not activated.

Main Menu

Better Timeline Shapes!

Started by hidden_hunter, June 05, 2009, 11:23:53 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

hidden_hunter

Microsoft really need to clean up the timeline shapes in Visio, they're kind of buggy (especially if you try and overlay things on top of them - the timeline intervals will always force themselves to the top)

I know some of you might say use a proper scheduling program but I use visio to make timelines that don't look poor which in turn a much easier to "sell" to the business (presentation is often 50% of the battle sadly)

wapperdude

Scheduling tool is typically the Gantt chart, but, that probably doesn't meet your visual pizazz factor.
Visio 2019 Pro

wapperdude

The interval shapes do like to be on top, but, that can be altered.  Place a shape you want on top, somewhere on the page.  Then, either press the key combination <cntl> + <shift> + <F> or go to the menu bar > Shape > Order > Bring to front.  This will elevate the shape to the front most position.  Now it will be on top of any interval that you've already placed.   ;)  However, any newly placed interval will take precedence over these shapes.   You'll just have to bring them or any new shape to the front.   :P  Moral of this story -- place all of the intervals 1st.   ::)

HTH
Wapperdude
Visio 2019 Pro

Browser ID: smf (possibly_robot)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 4: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 174 (show)
Files included: 34 - 1306KB. (show)
Memory used: 1052KB.
Tokens: post-login.
Cache hits: 13: 0.00208s for 26,726 bytes (show)
Cache misses: 2: (show)
Queries used: 15.

[Show Queries]