Community
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"MechMan" <mechman> wrote in messageI
href="news:f122f90.0@WebX.maYIadrTaRb">news:f122f90.0@WebX.maYIadrTaRb...
don't know if SP1 addresses this or not but I do know that Adesk is trying to
work it out so we have this ability again.
MechMan
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Gary R Smith (Autodesk)" <
href="mailto:gary.r.smith@autodesk.com">gary.r.smith@autodesk.com>
wrote in message
href="news:CCB9A228494E5C785D0BAA6CDFC07768@in.WebX.maYIadrTaRb">news:CCB9A228494E5C785D0BAA6CDFC......
This was not addressed in SP1 because it is not a
"bug".
As has already been discussed, the reasons I
disabled this workaround to the "organization" problem may not be valid and
simply adding it back may be the easiest thing to do in the short-term.
Longer-range ideas for addressing organization within an assembly are also
being considered.
Gary R. Smith -
Inventor Team
Autodesk DSD - Manufacturing Product Design
Portland,
OR
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Sean Dotson" <sean at sdotson dot com> wrote in message
href="news:89A068EB580B5CFFBB9A4E14761A7220@in.WebX.maYIadrTaRb">news:89A068EB580B5CFFBB9A4E14761......
Gary I think Mech (and I know I) knew it was not
a bug. We were part of the discussion before. Sorry if we made it
sound that way...
--
Sean Dotson, PE
href="http://www.sdotson.com">http://www.sdotson.com
...sleep is for
the weak..
-----------------------------------------
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Gary R Smith (Autodesk)" <
href="mailto:gary.r.smith@autodesk.com">gary.r.smith@autodesk.com>
wrote in message
href="news:CCB9A228494E5C785D0BAA6CDFC07768@in.WebX.maYIadrTaRb">news:CCB9A228494E5C785D0BAA6CD......
This was not addressed in SP1 because it is not
a "bug".
As has already been discussed, the reasons I
disabled this workaround to the "organization" problem may not be valid and
simply adding it back may be the easiest thing to do in the short-term.
Longer-range ideas for addressing organization within an assembly are also
being considered.
Gary R. Smith -
Inventor Team
Autodesk DSD - Manufacturing Product Design
Portland,
OR
size=2>
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Gary R Smith (Autodesk)" <
href="mailto:gary.r.smith@autodesk.com">gary.r.smith@autodesk.com>
wrote in message
href="news:C9CDA31A2D0378AB9BC8944F6802E803@in.WebX.maYIadrTaRb">news:C9CDA31A2D0378AB9BC8944F680......
I realize that the ability to drag things up and
down, while adding nothing as far as "design intent" to the model, did provide
a bit of organizational order to assemblies - via the browser view. My hope
was that we'd get generic folder capabilities to satisfy the
organizational need and my concern was that if we moved to a sequence
dependent browser view in assemblies like we have in part, then a part's
location in the browser could/would impact its interaction with assembly
features before/after. I was also thinking about including an "end of
assembly" node that behaved like the "end of part" node.
Given how we have segregated assembly features -
my reasons for disabling the up/down dragging seem to be invalid and painful
in light of not getting the generic folder organization "tool".
G