Stats

  • Replies 2
  • Subscribers 18
  • Views 9708
  • Members are here 0
More Content

Force axlDBCreateShape() to not define a shape as a rectangle?

mstaub

Does anyone know a way to force the function axlDBCreateShape() to NOT define a shape as a rectangle when the o_polygon/r_path coordinates just happen to form a rectangle? For example I am using axlDBCreateShape() to create shapes in a design. In instances where the shape is rectangular, this function now defines the shape as a rectangle (as seen using shape->isRect or 'FILLED RECTANGLE' when using show element). When I draw this exact same shape using "Shape Add", the shape is always defined as a shape (nil for shape->isRect or 'SHAPE' when using show element).

The reason I don't want it to be defined as a rectangle is because I am later trying to modify the shape using axlDBOpenShape(). If the new shape outline is not a rectangle, this function won't modify the shape outline and return nil.

Parents
  • mstaub

    ...And 10 minutes after posting this I found the solution.

    When looking at the documentation for axlDBCreateCloseShape(o_shape [g_forceShape]) I noticed it had the following parameter and description:

    g_forceShape

    By default, Allegro creates a rectangle in its database when an outline is a rectangle. This is for performance and space reasons. To override this behavior, pass the argument value as t when closing a shape.

    My guess is that since axlDBCreateShape()  is essentially a wrapper for axlDBCreateOpenShape() and axlDBCreateCloseShape() with no way to set g_forceShape, it's causing my shapes to be defined as rectangles. I have since changed my code to use axlDBCreateOpenShape() and axlDBCreateCloseShape() and set g_forceShape to 't' rather than using axlDBCreateShape() and everything is working as expected now!

  • Grungy Remnant
    in reply to mstaub

    Thanks for the solution update.  I was having the same issue. :)

Reply
  • Grungy Remnant
    in reply to mstaub

    Thanks for the solution update.  I was having the same issue. :)

Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.