Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/import.php on line 29

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/import.php on line 32

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JRequest::clean() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/import.php on line 33

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/request.php on line 463

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/request.php on line 464

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/request.php on line 465

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/request.php on line 466

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/request.php on line 467

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/request.php on line 468

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/import.php on line 35

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/import.php on line 38

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/import.php on line 39

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/import.php on line 46

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/import.php on line 47

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/import.php on line 50

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/import.php on line 53

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/import.php on line 54

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/import.php on line 57

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/import.php on line 58

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JFactory::getApplication() should not be called statically in /home/qghfomyp/public_html/index.php on line 31

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Redefining already defined constructor for class JObject in /home/qghfomyp/public_html/libraries/joomla/base/object.php on line 57

Strict Standards: Non-static method JApplication::getInstance() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/factory.php on line 46

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JApplicationHelper::getClientInfo() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/application/application.php on line 132

Strict Standards: Declaration of JSite::getRouter() should be compatible with & JApplication::getRouter($name = NULL, $options = Array) in /home/qghfomyp/public_html/includes/application.php on line 0

Strict Standards: Declaration of JSite::getPathWay() should be compatible with & JApplication::getPathway($name = NULL, $options = Array) in /home/qghfomyp/public_html/includes/application.php on line 0

Strict Standards: Declaration of JSite::getMenu() should be compatible with & JApplication::getMenu($name = NULL, $options = Array) in /home/qghfomyp/public_html/includes/application.php on line 0

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/registry/registry.php on line 19

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Declaration of JSession::set() should be compatible with JObject::set($property, $value = NULL) in /home/qghfomyp/public_html/libraries/joomla/session/session.php on line 0

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/session/session.php on line 19

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /home/qghfomyp/public_html/libraries/joomla/import.php:29) in /home/qghfomyp/public_html/libraries/joomla/session/session.php on line 423

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/qghfomyp/public_html/libraries/joomla/import.php:29) in /home/qghfomyp/public_html/libraries/joomla/session/session.php on line 423

Warning: Cannot modify header information - headers already sent by (output started at /home/qghfomyp/public_html/libraries/joomla/import.php:29) in /home/qghfomyp/public_html/libraries/joomla/session/session.php on line 426

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/html/parameter.php on line 21

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Declaration of JRegistryFormatINI::objectToString() should be compatible with JRegistryFormat::objectToString(&$object) in /home/qghfomyp/public_html/libraries/joomla/registry/format/ini.php on line 0

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JPluginHelper::importPlugin() should not be called statically in /home/qghfomyp/public_html/index.php on line 41

Strict Standards: Non-static method JPluginHelper::_load() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/plugin/helper.php on line 92

Strict Standards: Non-static method JPluginHelper::_import() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/plugin/helper.php on line 97

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Redefining already defined constructor for class JPlugin in /home/qghfomyp/public_html/libraries/joomla/plugin/plugin.php on line 75

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Declaration of JEvent::update() should be compatible with JObserver::update() in /home/qghfomyp/public_html/libraries/joomla/event/event.php on line 29

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JDispatcher::getInstance() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/plugin/helper.php on line 140

Strict Standards: Non-static method JPluginHelper::getPlugin() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/plugin/helper.php on line 147

Strict Standards: Non-static method JPluginHelper::_load() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/plugin/helper.php on line 41

Strict Standards: Non-static method JPluginHelper::_import() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/plugin/helper.php on line 97

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JDispatcher::getInstance() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/plugin/helper.php on line 140

Strict Standards: Non-static method JPluginHelper::getPlugin() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/plugin/helper.php on line 147

Strict Standards: Non-static method JPluginHelper::_load() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/plugin/helper.php on line 41

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JPluginHelper::_import() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/plugin/helper.php on line 97

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JDispatcher::getInstance() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/plugin/helper.php on line 140

Strict Standards: Non-static method JPluginHelper::getPlugin() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/plugin/helper.php on line 147

Strict Standards: Non-static method JPluginHelper::_load() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/plugin/helper.php on line 41

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/cache/cache.php on line 19

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Declaration of JCacheStorage::get() should be compatible with JObject::get($property, $default = NULL) in /home/qghfomyp/public_html/libraries/joomla/cache/storage.php on line 0

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JRequest::getInt() should not be called statically in /home/qghfomyp/public_html/index.php on line 55

Strict Standards: Non-static method JRequest::getVar() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/request.php on line 179

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JRequest::getCmd() should not be called statically in /home/qghfomyp/public_html/index.php on line 67

Strict Standards: Non-static method JRequest::getVar() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/request.php on line 255

Strict Standards: Non-static method JRequest::_cleanVar() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/request.php on line 140

Strict Standards: Non-static method JFilterInput::getInstance() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/request.php on line 577

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/document/document.php on line 19

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Declaration of JDocumentRendererRSS::render() should be compatible with JDocumentRenderer::render($name, $params = Array, $content = NULL) in /home/qghfomyp/public_html/libraries/joomla/document/feed/renderer/rss.php on line 31

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Only variables should be assigned by reference in /home/qghfomyp/public_html/libraries/joomla/document/feed/renderer/rss.php on line 53

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/qghfomyp/public_html/libraries/loader.php on line 186

Strict Standards: Non-static method JResponse::toString() should not be called statically in /home/qghfomyp/public_html/index.php on line 88

Strict Standards: Non-static method JResponse::getBody() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/response.php on line 190

Strict Standards: Non-static method JResponse::allowCache() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/response.php on line 197

Strict Standards: Non-static method JResponse::setHeader() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/response.php on line 199

Strict Standards: Non-static method JResponse::setHeader() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/response.php on line 200

Strict Standards: Non-static method JResponse::setHeader() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/response.php on line 201

Strict Standards: Non-static method JResponse::setHeader() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/response.php on line 202

Strict Standards: Non-static method JResponse::setHeader() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/response.php on line 203

Strict Standards: Non-static method JResponse::sendHeaders() should not be called statically in /home/qghfomyp/public_html/libraries/joomla/environment/response.php on line 206
Revit Hints and Tips Revit Store providing Families and Training Videos for Autodesk Revit platforms http://revitstore.com/index.php?option=com_content&view=section&id=3&Itemid=55 Wed, 19 Sep 2018 15:08:10 +0000 Joomla! 1.5 - Open Source Content Management en-gb Family Templates - Designed Use http://revitstore.com/index.php?option=com_content&view=article&id=84:family-templates-designed-use&catid=34:revit-family-templates&Itemid=55 http://revitstore.com/index.php?option=com_content&view=article&id=84:family-templates-designed-use&catid=34:revit-family-templates&Itemid=55 This document sets out what each family template is design for. This document is not complete - it originally was meant to show users the main templates that might not be as apparent as others.

]]>
ihoward@4thdimensionsoftware.com (Ian Howard) Revit Family Templates Wed, 21 Jan 2009 21:20:47 +0000
Redline Mark-ups http://revitstore.com/index.php?option=com_content&view=article&id=153:redline-mark-ups&catid=37:tips-and-tricks&Itemid=55 http://revitstore.com/index.php?option=com_content&view=article&id=153:redline-mark-ups&catid=37:tips-and-tricks&Itemid=55

Redlining

Redlining – changing attitudes and workflow.

We don’t need to go back so far in time to see life changing attitudes and workflows. Here’s a typical one most people can relate to, that of recycling at Home and in the Office. Most of us were gently persuaded into recycling, but now wouldn’t think twice about it.

Traditional Workflow – (for marking up changes to drawings).

Traditionally drawings are marked up in red pen with required changes. These hardcopy mark-ups are then handed to someone to make the necessary changes to the electronic document.

Traditional Workflow Analysis:

  • Someone prints or receives the original print to mark up.
  • The Print is then fully marked up with changes in Red pen.
  • The Marked up print is then either:
    Handed to another person in that Office.
    OR
    Scanned electronically and emailed/or transferred via ftp.

  • The marked up is then received so changes can be made, either:
    Handed to the person responsible for making the changes, within that Office
    OR
    Scanned Document downloaded and Printed off for reference in making the necessary changes to the document.

  • The individual makes the changes having to transfer the changes from a paper form onto his/her computer screen. Therefore potential for missing an item requiring change.


All this creates lots more work, expense and also cost to the environment in all that extra paper!

A more streamlined approach is by utilising the Redlining capabilities in the Autodesk product range. So the company line is to embrace and utilise Redlining.


Reasons for resisting change.

The most common point for opposing a change to electronic marking up is generally “I need to see the whole picture. I can’t easily see on screen what I see on a hardcopy print”.

My response to this is simple, instead of felling two trees, lets fell one – at least we save on paper and also we can save double handling. What I’m getting at is print/receive the original by all means, so you can “see the whole picture” and try an alternative workflow like the one below:

Alternative Workflow Analysis:

  • Someone prints or receives the original print.
  • Bubble up areas loosely, where you identify change requirements. Important thing is you don’t spend time marking up with comments.
  • Now produce a DWF file of the same drawing, unless you have one already. Give it a name that corresponds with the drawing number including the revision, eg: 150c, for Drawing 150 revision C. If you have received a DWF from the other party, you can mark this one up.
  • Open this DWF file using Autodesk Design Review.
  • Zoom into those areas identified on your hardcopy print and fully mark up with Bubbling and comments. Note additional information can be attached to your mark-up, such as Image files and additional DWF files (these might convey additional detail where you don’t want to draw inside Design Review when you already have say a standard detail you wish them to emulate).
  • Save the DWF file.

  • Point the person making the changes to the location of the DWF.
    OR
    the DWF file is emailed/or transferred via ftp.
  • The DWF mark-up is then linked into Revit. The DWF knows which sheet it is linked with, so automatically displays the relining in the correct sheet/view.
  • Now the individual making the changes can see both the relining and his/her model together on screen, therefore making the changes faster and potentially with no omissions (based on the method of working).

Benefits of using Electronic Marking up.

  • The electronic document may be filed for quick reference in the future. (Manual process means storing lots of paper, also retrieving the manual mark-up often is hampered by “I can’t lay my hands on it right away, I’m sure it should be here, somewhere”).
  • Changes between revisions to drawings may be compared in DWF files. This would aid your knowledge on adding revision notes.
    Eg: After making numerous changes to your Revit model, you can publish a temporary DWF file and compare this to the previous one. The Compare function will highlight what has changed, therefore you can fully itemise all the changes since the last issue of that drawing.

 

How to use Redline in Revit.

First time export to 2D DWF

  • Once you receive the marked-up version of the DWF back, then you will need to link the DWF marking set into Revit. From the ‘Link Ribbon’ of the ‘Insert Ribbon’ choose DWF Markup
  • Make the changes to the view.

Second time export

  • Within Manage Links, remove the previous DWF Markup, or
    In Visibility, under the Imported Categories tab, turn off the markup objects from the DWF file – otherwise these will be added to the drawing information as though they are part of the drawing. Turning the Redlining off will mean that the DWF is clear of any previous comments/notes, so it may be marked up upon the next revision.
  • Upon receiving a new copy of the DWF marked-up:
    You can either attach the Markup using Manage Links or if the DWF links remains in the project, then you can use Manage Links to refresh the DWF Markup.
  • Make additional changes to your view.
  • In future exports to DWF, remember to either remove the old Markup using Manage Links, or turn off markup objects in Visibility Graphics.

Using Autodesk Design Review

Design Review is a simple to use package that allows you to mark-up changes that are required to documents, normally drawings. You can simply add bubbled areas and text to communicate your changes.

Redlining_1

As well as simply marking up, Design review allows you to attach all manner of accompanying files to back-up your required changes/marking up.

Procedure – including attachments within a DWF:

  • Open up DWF file that you wish to mark-up.
    Redlining_2
  • Once open you will see the drawing sheet within the list view.
  • Additional documents may now be dragged and dropped into the ‘List View’ window/palette.
    Redlining_3
  • You can attach a number of different file formats, including pdf/images/other dwf files.
  • When saved, these files will be added to the original dwf file. Notes making reference to these attachments may be made, therefore clarifying the changes needed to be made.

DWF Compare

You can compare a couple of DWF files, when compared the additions and deletions will be highlighted in Red and Green.

Redlining_4

Comparing DWF files can be useful to highlight all that has changed since the last issue, therefore making the revision note more accurate.


 

Written By: Ian Howard
© RevitStore

]]>
ihoward@4thdimensionsoftware.com (Ian Howard) Tips and Tricks Fri, 04 Feb 2011 22:00:05 +0000
Autodesk Labs http://revitstore.com/index.php?option=com_content&view=article&id=154:autodesk-labs&catid=35:links&Itemid=55 http://revitstore.com/index.php?option=com_content&view=article&id=154:autodesk-labs&catid=35:links&Itemid=55 Autodesk Labs

Click Image Below...

Autodesk_Labs_Link

 

]]>
ihoward@4thdimensionsoftware.com (Ian Howard) Links Fri, 12 Aug 2011 08:48:17 +0000
Revit Family - Catalog Files http://revitstore.com/index.php?option=com_content&view=article&id=65:revit-family-catalog-files&catid=31:tips&Itemid=55 http://revitstore.com/index.php?option=com_content&view=article&id=65:revit-family-catalog-files&catid=31:tips&Itemid=55 Family Catalog files are  comma-delimited TXT files that have the same name as the family. Also the txt file has to be stored in the same location as the Family.

]]>
ihoward@4thdimensionsoftware.com (Ian Howard) Family Editor Tue, 10 Mar 2009 11:30:01 +0000
Family Templates - Metric Baluster.rft http://revitstore.com/index.php?option=com_content&view=article&id=63:family-templates-designed-use&catid=34:revit-family-templates&Itemid=55 http://revitstore.com/index.php?option=com_content&view=article&id=63:family-templates-designed-use&catid=34:revit-family-templates&Itemid=55 Family Template: Metric Baluster.rft

Images Examples:

This family is designed to be used for some of the following:
Stair Baluster/Spindle

Writen By: Ian Howard
© RevitStore

]]>
ihoward@4thdimensionsoftware.com (Ian Howard) Revit Family Templates Wed, 21 Jan 2009 21:20:47 +0000
Mike Hardy-Brown Blog site http://revitstore.com/index.php?option=com_content&view=article&id=150:mike-hardy-brown-blog-site&catid=35:links&Itemid=55 http://revitstore.com/index.php?option=com_content&view=article&id=150:mike-hardy-brown-blog-site&catid=35:links&Itemid=55 Mike Hardy-Brown Blog Site

Click Image Below...

mhb_blogg

 

]]>
ihoward@4thdimensionsoftware.com (Ian Howard) Links Tue, 14 Sep 2010 09:31:14 +0000
Ultimate Detailing http://revitstore.com/index.php?option=com_content&view=article&id=152:ultimate-detailingcoordination&catid=37:tips-and-tricks&Itemid=55 http://revitstore.com/index.php?option=com_content&view=article&id=152:ultimate-detailingcoordination&catid=37:tips-and-tricks&Itemid=55 Ultimate Detailing and Co-ordination
How to detail in Revit (Best Practice)…

 

Detailing in Revit may be done in a number of ways, some more effective than others. This section sets out an extremely effective way to detail and coordinate detailing in Revit. If you prefer to detail in another method there are still points that can be taken away from this and potentially incorporated in your preferred method of detailing.

 

Co-ordination views and use of Groups is key to effective Detailing in Revit, without this the project details can become less manageable and more time is eaten up in their upkeep.

 

As there are two forms of Detailing, “Hybrid” and “Complete over-Detailing”, it is more important to focus on two points (Co-ordinated Views and Groups), than in which type of Detailing method you adopt. However the following method describes in detail the later style of Detailing, but this may be adapted to suit the Hybrid version as well.

 

Two forms of Detailing:

 

“Hybrid” Detailing is drawing additional information over the detail view, so the detail produced is a combination of 2D information and the 3D model behind.

“Complete over-Detailing” is where the 3D model is used to trace over in 2D; with the 3D model turned off on completion of the detail.

 

Co-ordinating your Details and Model

Essentially, we create a number of duplicated views, including sections and plans that are detailed in the areas of the callout details. These views display the 3D model in an underlay form, so that coordination between the 2D Detailing and 3D model can be viewed together to see how each affects the other. Coordination detailing (Brick/Block Coursing etc...) is added between these detail areas. All the Detailing in these views are then made into detail groups (this can consist of nested groups), that can then be added to each detail on your sheet views.

 

In this way, as the Working Detailing is amended, this automatically amends all the details on your sheets – all that remains is to check for amendments to annotation within those sheets prior to revising and issuing them.

 

Smarter Views

When creating the coordinated detail views in plan and section, as well as your detail callouts, this may be done in the usual way; However, you can utilise the use of Dependant views as the basis for extremely effective detailing, this is potentially the best method and the one that we will run through in the following procedures.

 

Use of Detail Groups

Detail Groups are useful in detailing for a number of reasons:

They can be saved out for use on other projects – don’t think of these as Standard details, but think of them in this way as a quick method of loading them into another project saving you much time in loading and assembling detail components together. Even if the detail group you load is only 60% of the information you require in your new detail, this will save valuable time in making the detail from scratch.

Another reason for using Detail Groups is for common areas between similar details. For example a Window head/Lintel section that is the same within the Window section and Door Section details, or in the case of the image below a window reveal is repeated in a number of details.

Detailing_1

Note: Detail groups should always be made up of other nested groups wherever applicable. Groups should be made for a repeating unit. Therefore for a completed detail of a Strip Section, this could typically consist of a nesting of groups for the Window Section with Cill and window boards, a group for the Lintel Head detail and any other details that will likely be utilised in other sectional details e.g. Typical Eaves Detail.

DetailSmart 1

Highlighted Green Areas indicate ‘Detail Areas’

Highlighted Pink Areas indicate ‘Coordinated Detailing’ between ‘Detail Areas’


Procedure (Detailing Best Practice):

 

  • After creating GA Plans and GA Sections.
  • Create Callouts in the GA’s at the desired scale for your details. Make the Callout the same overall size as the General Arrangement.

    Detailing_3
  • Hide these Callouts in your GA views.
  • Name these Callouts

    For Section Views:
    Eg: “Coordinated Detailing – Section A 1-5

    For Plan Views:
    Eg: “Coordinated Detailing – 00_Ground 1-5

    These views will become working views that you can coordinate the 2D detailing and the 3D Model. Further to this the view will show the outlines of all your callout details, these areas may be detailed fully in this coordinated view along with detailing that needs to be coordinated between the details.
  • Next, duplicate this view as a Dependant view.
  • Rename this new view as you would for your detail.
    eg:       Detail A – Window Head
    Detail B – Wall Head restraint
  • Select the Crop Region and resize the boundary to the area of your detail.
  • Repeat this for all your details, by creating Dependant views from the coordinated view.

    Detailing_4
  • Go back into your original GA Plans/GA Sections and notice all the callouts of your details. Amend the location of the Callout Annotation/Tag, and position it so it will be readable.
  • Now go back into your Coordinated Detailing view (Parent view to all the Dependant details).
  • In the Views Properties, change the parameter ‘Display Model’ to ‘Halftone’.

    Detailing_5
  • This will dim out the Model geometry making it easier to see what you have detailed in 2D.
    Detail this view up so that it includes all the required Detailing for your sheet views, as well as including any detailing that is necessary to link all the details together for Vertical/Horizontal coordination e.g. Brick/Block coursing in section.

    Detailing_6

    Remember that although the underlayed Model is in outline form in the view it is still live, therefore can be selected for change, or if you are not careful accidentally selected and deleted!
  • Once the details are complete, the parameter ‘Display Model’ will be set to ‘Do not Display’.
  • Place all the details on sheets.

    The coordination of the 2D details and the 3D Model may be monitored by simply toggling the ‘Display Model’ parameter within the Coordinated views. It must be remembered that this parameter must be set to ‘Do not Display’ once the coordination has been checked as this setting is changed in both the coordination view and the dependant detail views.

    Note: Even though the project browser can filter out views placed on sheets, this does not apply to dependant views. Therefore a system needs to be developed so that it is clear those dependant views that have been placed on sheets and though awaiting placement. A possible solution is to prefix the view name with the sheet number once placed on a sheet. The image below demonstrates which of these details are not yet placed on sheets.

    Detailing_7


Written By: Ian Howard
© RevitStore

]]>
ihoward@4thdimensionsoftware.com (Ian Howard) Tips and Tricks Fri, 04 Feb 2011 00:00:00 +0000
Family Templates - Metric Baluster-Panel.rft http://revitstore.com/index.php?option=com_content&view=article&id=67:family-templates-designed-use&catid=34:revit-family-templates&Itemid=55 http://revitstore.com/index.php?option=com_content&view=article&id=67:family-templates-designed-use&catid=34:revit-family-templates&Itemid=55

Family Template: Metric Baluster-Panel.rft

Images Examples:

This family is designed to be used for some of the following:
Stair Panelling that spans between Newel and Intermediate Posts

Writen By: Ian Howard
© RevitStore

]]>
ihoward@4thdimensionsoftware.com (Ian Howard) Revit Family Templates Wed, 21 Jan 2009 21:20:47 +0000
2011 Properties UI fix http://revitstore.com/index.php?option=com_content&view=article&id=151:2011-properties-ui-fix&catid=37:tips-and-tricks&Itemid=55 http://revitstore.com/index.php?option=com_content&view=article&id=151:2011-properties-ui-fix&catid=37:tips-and-tricks&Itemid=55 Some of you may have seen that there are still a couple of User Interface issues around in Revit 2011. There are two that constantly annoy, the first I have no fix for, but I have a solution for the other.

Properties and Project Browser Issue:
As a default the Project Browser and Properties Palette are  vertically stacked having an equal height. If the two are left as a 50-50 split, then the system works OK. However, if you drag one panel to increase or decrease the ratio, then more often than not the lower panel collapses downwards. This generally happens when you swap between views or between project and family views. From then on you are constantly dragging the panels up and at some point they collapse downwards again. I can’t find any other reference to this, but have seen it hundreds of times on numerous Machines. Hopefully Autodesk sort this shortly.

Type Properties Issue:
Have you noticed the annoying type properties that leaps sideways each time you go to amend a parameter value. Each time you change a value it leaps sideways again. There is a slide control at the base that you then have to slide to the left to see the parameters once again, but as soon as you pick another value it constantly slides to the right!
This fix is not a software fix, just a simple manual fix (hopefully Autodesk will see and fix this in future releases). So, the fix is to drag the division between the two columns. Drag this slightly to reduce the column ‘Parameter’.

2011 Type Properties Fix

 

Within your current session of Revit, this should fix the issue. However, next time you start Revit up this will revert back.

Written By: Ian Howard
© RevitStore

]]>
ihoward@4thdimensionsoftware.com (Ian Howard) Tips and Tricks Sun, 23 Jan 2011 14:10:38 +0000
Design Reform Blog http://revitstore.com/index.php?option=com_content&view=article&id=149:design-reform-blog&catid=35:links&Itemid=55 http://revitstore.com/index.php?option=com_content&view=article&id=149:design-reform-blog&catid=35:links&Itemid=55 David Fano's Blog Site

Click Image Below...

Design_Reform_Blog

]]>
ihoward@4thdimensionsoftware.com (Ian Howard) Links Sat, 04 Sep 2010 13:38:13 +0000