Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can call <code>glVertexPointer</code> with the base of your vertex array, and <code>glTexCoordPointer</code> with the base of the texture coords array. As long as the number of things in those arrays line up to the right (same) number of verts, this should work fine.</p> <p>OpenGL can't access members of the structure explicitly. The members will be laid out in memory next to eachother (see caveat below). If multiple Point structures are in a series in memory, effectively you have a big flat list of doubles. OpenGL doesn't know about structures, it just wants one big list of (double in this case) values. But you can build a series of Points and hand OpenGL a pointer to the first one, and if the layout in memory isn't wrong or padded, they'll be equivalent.</p> <p>If you're too new to C to have this conceptually under your belt (along with the memory layout caveats), then you should just copy all the doubles into a new array before calling GL. </p> <p>I do question a couple things: maybe there's missing code here, but having <code>Point**</code> instead of <code>Point*</code> looks fishy, since <code>glVertexPointer</code> etc will expect a flat array of values here. By the same token, although it's probably aligned fine already, in theory an array of those structs might not be flush-packed together in memory. You can do this explicitly depending on your compiler, or you can play with the <code>stride</code> param in the GL calls to be explicit about the distance in memory between each vert.</p>
    singulars
    1. This table or related slice is empty.
    1. POOpenGL Vertex Arrays
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBen Zotto
    1. USBen Zotto
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POOpenGL Vertex Arrays
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe issue is that the glVertexPointer expects a flat array of numbers, not Points*. I need some way of telling glVertexPointer that the coordinate data is in Point->x and Point->y without having to build a flat array.
      singulars
      1. PO
      1. USBrad Zeis
    2. COOh, and the Polygon has Point**s instead of Point*s is because Point is a Python Extension Type. The preferred way of working with Extension Types is to always manipulate pointers of them.
      singulars
      1. PO
      1. USBrad Zeis
    3. COI updated the answer with the C memory management info that I think is the understanding gap here. Use "memory polymorphism" only if you feel comfortable with what you're doing. And I don't know much about Python, so I'll assume you know what you're doing there. :)
      singulars
      1. PO
      1. USBen Zotto
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload