emtpy space in cellview when fit zoom

blankman said:

What other way can I use to minimize the cellview for the correct zoom fit

Unfortunately, I don't know of any magic bullet for this problem: you need to dig a little to find out what is pushing out the boundary.

That said, here are some things you can try:

geDeleteAllMarker(geGetWindowCellView())
mapc('dbDeleteObject setof(shape geGetWindowCellView()->shapes shape->lpp == '("marker" "drawing")))
when(fboundp('mgc_rve_delete_markers) mgc_rve_delete_markers())
dbComputeBBox(geGetWindowCellView())
hiRedraw()
geRefresh()

  --tom

I did think about writing something a bit more dedicated, but one approach would be to use the code example given in this post.

For example, you could do:

cv=geGetEditCellView()
abTreeExample(cv~>shapes)

you could also then use:

abTreeExample(cv~>instances)
abTreeExample(cv~>vias)
abTreeExample(cv~>mosaics)
abTreeExample(cv~>areaBoundaries)

and so on - other interesting attributes to look at might be figGroups, blockages, rows, markers, guides, routes, steiners.

The code allows you to sort the objects on the lower left x or y, or upper right x or y - so you can find the extent of each type of object. 

If I had more time I'd write something which just showed the bBox for each layer (say) and the bBox for each other kind of object, to give you more of a starting clue without necessarily showing every single object. But I don't, so I'll leave that as an exercise for the reader - or maybe the code above is sufficient for your needs.

Regards,

Andrew.

Thanks for the help and interest script.

Looks like the problem is guides in the cellview.

Does deleting the guideseffect anything in the layout environment, L or VXL?

Paul

Paul,

I'm Not sure of the answer. Please contact customer support as more research will be needed, probably.

Andrew.