Difference between revisions of "Error Messages/41249"
(Created page with '= Error Text = Cyclic module dependency. Mo3 - Mo2 - Mo1 - Mo3 Module Mo3 not moved = Cause = You have attempted to move a module node to another location, but in so doing…') |
|||
Line 1: | Line 1: | ||
− | + | [[Category: Error messages]] | |
+ | == Error text == | ||
+ | <pre style="background:white; border:white; margin-left: 1em; font-style:italic"> | ||
Cyclic module dependency. | Cyclic module dependency. | ||
Mo3 - Mo2 - Mo1 - Mo3 | Mo3 - Mo2 - Mo1 - Mo3 | ||
Module Mo3 not moved | Module Mo3 not moved | ||
+ | </pre> | ||
− | = Cause = | + | == Cause == |
− | |||
You have attempted to move a module node to another location, but in so doing, you are causing a module to be located within itself, which is not possible. To understand how this can happen, consider the following diagram hierarchy: | You have attempted to move a module node to another location, but in so doing, you are causing a module to be located within itself, which is not possible. To understand how this can happen, consider the following diagram hierarchy: | ||
− | + | <pre style="background:white; border:white; margin-left: 1em"> | |
Mo3 | Mo3 | ||
Mo2 | Mo2 | ||
Mo1 | Mo1 | ||
+ | </pre> | ||
− | This hierarchy depicts that Mo3 is a module of the top-level model, Mo2 is inside Mo3, and Mo1 is inside Mo3. | + | This hierarchy depicts that <code>Mo3</code> is a module of the top-level model, <code>Mo2</code> is inside <code>Mo3</code>, and <code>Mo1</code> is inside <code>Mo3</code>. |
− | Now suppose you were to attempt to move Mo3 into Mo1. This would place Mo3 inside Mo1, which is inside Mo2, which is inside Mo3 -- meaning that Mo3 would then be inside itself. The whole cycle would no longer be inside the model - there'd be no root parent any more. This is what a cyclic module dependency is, and it is not allowed. Thus, when you attempt an operation that would cause it to occur, this error appears. | + | Now suppose you were to attempt to move <code>Mo3</code> into <code>Mo1</code>. This would place <code>Mo3</code> inside <code>Mo1</code>, which is inside <code>Mo2</code>, which is inside <code>Mo3</code> -- meaning that <code>Mo3</code> would then be inside itself. The whole cycle would no longer be inside the model - there'd be no root parent any more. This is what a cyclic module dependency is, and it is not allowed. Thus, when you attempt an operation that would cause it to occur, this error appears. |
− | = Remedies = | + | == Remedies == |
+ | You can move an alias of a module into itself without any conflict. So, if you wanted quick access to the top level from within <code>Mo1</code>, you could create an alias of <code>Mo3</code> and drag it into <code>Mo1</code>. | ||
− | + | ==See Also== | |
+ | *[[Modules and Libraries]] | ||
+ | * [[Recursion]] |
Latest revision as of 19:08, 15 March 2016
Error text
Cyclic module dependency. Mo3 - Mo2 - Mo1 - Mo3 Module Mo3 not moved
Cause
You have attempted to move a module node to another location, but in so doing, you are causing a module to be located within itself, which is not possible. To understand how this can happen, consider the following diagram hierarchy:
Mo3 Mo2 Mo1
This hierarchy depicts that Mo3
is a module of the top-level model, Mo2
is inside Mo3
, and Mo1
is inside Mo3
.
Now suppose you were to attempt to move Mo3
into Mo1
. This would place Mo3
inside Mo1
, which is inside Mo2
, which is inside Mo3
-- meaning that Mo3
would then be inside itself. The whole cycle would no longer be inside the model - there'd be no root parent any more. This is what a cyclic module dependency is, and it is not allowed. Thus, when you attempt an operation that would cause it to occur, this error appears.
Remedies
You can move an alias of a module into itself without any conflict. So, if you wanted quick access to the top level from within Mo1
, you could create an alias of Mo3
and drag it into Mo1
.
Enable comment auto-refresher