Hello, wondering if anyone else is having this issue.
I have a series of block line works which I need to layer. and I would like to send some blocks behind other blocks. However when I run the command SendToBack, it does not allow to select a block object.
Thanks
Yes, I think all the display order stuff only works on actual curves and hatches.
There is a trick that might work for ‘bring to front’: use the gumball to move the block you want on top a short distance sideways and then move it back. This usually seems to bring it to the front. I don’t know whether this sticks permanently though.
Regards
Jeremy
thanks @Helvetosaur @jeremy5
didn’t get back sooner as my computer got stolen… : [.
Anyhow, @jeremy5 I tried moving the block and re positioning, however it still seems to keep its order…
one work around I have found is to physically move a block in the vertical plane. this is not ideal, as when drawing you get snaps on different planes, etc.
@Helvetosaur do you think there is away to resolve or add as a topic to fix?
Thanks,
Andrew
Dunno - the problem is that block instances can contain any number of types of objects, including those that do not have display order characteristics… I suppose that it’s possible to dive down into a block instance’s components and see if there are hatches/curves and apply the display order. I have no idea if the block instance construct supports that or what kind of work that might entail though. Maybe @jeff has an idea…
I wrote the draw order code and it just isn’t going to work with blocks n it’s current form. We probably need to completely rethink the whole draw order mechanism at some point in the future.
HI,
that would be a really handy feature if it could be added to a future…
I often am using blocks for layouts of architectural / interior spaces, and have a series of layers of informations, i.e Elec, furniture, air, mechanical, etc etc. And its good to have each of these sets on information on a block, so I can edit and it updates in other drawings. and when I have all those blocks on the same layout, it would be handy to be able to send those forward or back for when printing to PDF
unless you know of another way of doing this?
Thanks,
I’m a great fan of rhino and I love it very much! I never stopped working since I started in 2003 with architecture. The only situation I still need to switch to autocad for certain projects is exactly this issue with the missing draw-order for blocks. You simply can’t work with it in a professional way. I tried a million workarounds but no chance. Very annoying for such great software. It would be so great if this could get fixed.
Another thing which would be more than cool would be a function to somehow clip a block.
Thanks a lot.
I totally agree with @cwetteskind.
I’d really hoped this would be fixed in v7. However it is not. And unfortunately it makes Rhino inferior to the competitors when it comes to architectural drafting.
Dear developers, please take a look at draw order in blocks, since Rhino has a great potential to enter professional workflow in architecture field!
Is there any update on draw order working with blocks?
No updates. Rhino 7 will not have any changes made to draw order.
Understood. Will wait for the next version update for this.
Hi,
I am having the same problem, I want to send blocks in front of other blocks.
@stevebaer I assume there is no news on this topic, right?
Hey tobias,
Today I was dealing with the same issue and ended up writing up a command/script for it, part of a larger project.
Turns out block instance do have the property in there, it’s just that the command does not allow to select blocks.
Warning: It cycles through all the objects to know the highest value of DisplayOrder, so it might be slow on a heavy file
Here’s a screen recording:
And the script (downloadble file below):
# SPDX-License-Identifier: MIT
import Rhino
import scriptcontext as sc
import rhinoscriptsyntax as rs
__commandname__ = "DisplayOrder"
def modalEnumSelect(title, enum):
"""
Modal input in Rhino commandline.
Args:
title (str): text that appears in the command prompt.
enum (list of str):
Returns:
The new chosen value.
"""
go = Rhino.Input.Custom.GetOption()
go.SetCommandPrompt(title)
optMap = {}
for key in enum:
optIndex = go.AddOption(key)
optMap[optIndex] = key
while True:
go.Get()
result = go.Result()
if result == Rhino.Input.GetResult.Cancel:
return Rhino.Commands.Result.Cancel
elif result == Rhino.Input.GetResult.Option:
optIndex = go.OptionIndex()
if optIndex in optMap.keys():
return optMap[optIndex]
else:
raise NotImplementedError("OptionIndex: %s" % optIndex)
def GetObjects(
message="Select Objects",
preselect=True,
select=False,
group=True,
minimum_count=1,
maximum_count=0,
):
if not preselect:
sc.doc.Objects.UnselectAll()
sc.doc.Views.Redraw()
go = Rhino.Input.Custom.GetObject()
go.SetCommandPrompt(message)
go.SubObjectSelect = False
go.GroupSelect = group
go.AcceptNothing(True)
if go.GetMultiple(minimum_count, maximum_count) != Rhino.Input.GetResult.Object:
return []
if not select and not go.ObjectsWerePreselected:
sc.doc.Objects.UnselectAll()
sc.doc.Views.Redraw()
result = []
count = go.ObjectCount
for i in range(count):
object = go.Object(i).Object()
result.append(object)
if select and object is not None:
object.Select(select)
go.Dispose()
return result
def RunCommand(is_interactive):
objects = GetObjects()
if len(objects) > 0:
modeEnum = [
"Log",
"Set",
"BringForward",
"BringToFront",
"SendBackward",
"SendToBack",
]
mode = modalEnumSelect(__commandname__, modeEnum)
maxDisplayOrder = 0
minDisplayOrder = 0
for object in sc.doc.Objects:
objectDisplayOrder = object.Attributes.DisplayOrder
maxDisplayOrder = max(maxDisplayOrder, objectDisplayOrder)
minDisplayOrder = min(minDisplayOrder, objectDisplayOrder)
if mode == "Log":
for object in objects:
print("Display Order = %s" % object.Attributes.DisplayOrder)
elif mode == "Set":
value = rs.GetInteger("Set")
if isinstance(value, int):
for object in objects:
object.Attributes.DisplayOrder = value
object.CommitChanges()
else:
return Rhino.Commands.Result.Cancel
elif mode == "BringForward":
for object in objects:
object.Attributes.DisplayOrder += 1
object.CommitChanges()
elif mode == "BringToFront":
for object in objects:
object.Attributes.DisplayOrder = maxDisplayOrder + 1
object.CommitChanges()
elif mode == "SendBackward":
for object in objects:
object.Attributes.DisplayOrder -= 1
object.CommitChanges()
elif mode == "SendToBack":
for object in objects:
object.Attributes.DisplayOrder = minDisplayOrder - 1
object.CommitChanges()
else:
print("Not Implemented OptionIndex: %s" % mode)
return Rhino.Commands.Result.Success
else:
return Rhino.Commands.Result.Cancel
if __name__ == "__main__":
RunCommand(False)
DisplayOrder.py (3.9 KB)
This will work to a point, but also may cause what some would consider bugs. This is why the setting of DisplayOrder is not available for blocks in the built in Rhino commands. For example if your block contains any sort of surface geometry, things will not look correct in a shaded view.
Got it, I only use it for printing (and only hatches and curves) and I’m happy to report it has worked so far.
Thank you for the heads up