I'm experiencing a really strange phenomena. I'm attempting to stylize my list/grid for an inventory GUI I'm building. Styling the columns and everything else in this window is working out just fine. But something very strange is happening with my attempt to set the text color of the text in the List's rows. It seems, for one, to ignore my color specification altogether. But it also seems to render the text a different color everytime I hide/show my Inventory window. I have it rigged up, naturally, to hide and show when hitting the "I" key. I'll show it, the text will be pink, I'll hide it, then show it, and the text is purple, I'll hide it, then show it, and the text is black. And it only seems to affect the text in the rows. The column text styles properly, and the background color behind the rows and all the other styles I'm setting within this window seem to be doing what they are suppose to.
I recently tried a variation on the above code by using a TextDS object and setting the Lists tds property. It made the text color correct, but the letters were all screwed up, as if they were all on top of one another, forming one, single illegible letter. Is there no one else thats gotten this to work?
So thats using the tds property of List and the end result I'm getting is shown in the attached screenshot (it should say something like name - club, damage - 20, value - 5). Using the approach in my first post in this thread, it displays the values correctly, but with a different color everytime I show the window. Using this approach I just pasted in this post, its showing the right color, but the text is all screwy.
Oh I see what you are talking about now. You must be referring to Properties - Class Member Editing.cpp. I didn't make the connection with that tutorial and what I was attempting to do here.
I think it would be nice to, at some point, have some solid documentation on each function/property for each object type in the API that has a clear description of what each member does and an example of each member being used. The tutorials provide a good general overview of the concepts behind the way things work in your API but sometimes its like going on a treasure hunt to find exactly what I'm looking for and its not always clear where I need to look.
Yea, I read the header files. I read everything. I just didn't make the connection that members had to be members of the same class or struct they are being used for. I thought it could be a member of any class or struct.