I finally got around to upgrading from 1.13 to 1.14A and found a
problem/difference I can see refered to nowhere. If I create a PtGraphic
derived widget at run time, whose owner is a PtGrid (I am placing a graph on
a grid), the effective origin doesn’t seem to be the grid, but the base
widget itself. The Pt_ARG_GRAPHIC_FLAGS choices don’t seem to effect this.
I worked around the problem by making the ABW_base the parent, and handling
the origin manually, but I am nervous there are other changes I missed. Was
I doing something wrong from the beginning, which just happened to work, or
was there a real (at least nearly) silent change.
TIA
Gary
“Gary Hubbard” <ghubbar @sandia.gov> wrote:
: I finally got around to upgrading from 1.13 to 1.14A and found a
: problem/difference I can see refered to nowhere. If I create a PtGraphic
: derived widget at run time, whose owner is a PtGrid (I am placing a graph on
: a grid), the effective origin doesn’t seem to be the grid, but the base
: widget itself. The Pt_ARG_GRAPHIC_FLAGS choices don’t seem to effect this.
: I worked around the problem by making the ABW_base the parent, and handling
: the origin manually, but I am nervous there are other changes I missed. Was
: I doing something wrong from the beginning, which just happened to work, or
: was there a real (at least nearly) silent change.
PtGrid isn’t a descendant of PtContainer, so it can’t have any children. Your
graphic is really a child of whatever container the grid is in. To confirm
this in PhAB:
- create the grid and a graphic
- check out the Module Tree control panel
Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems