<br><br><div class="gmail_quote">On Tue, Jan 6, 2009 at 1:31 AM, 0xDeadC0de <span dir="ltr"><<a href="mailto:roguestar191@comcast.net">roguestar191@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
<br>
Note, the version I sent to the mailing list... had problems. The<br>
version I have still does, I can't get any zorder's to be respected and<br>
randomly(near it's a computer I know nothing is really random in them)<br>
the combo box's will be behind or in front of things. the Qt guys say<br>
"Shouldn't do that with proper parenting", Aaron said "Try raising z<br>
values". I tried both, separately, and together, just get bad or no<br>
results. I'm new to Qt too though so it very well could be my fault,<br>
although I have it on good authority it's likely a Qt bug.</blockquote><div>Yes, i would be surprised if that was something to do with the ruby bindings, but not impossible. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
I applied for KDE svn, will put the "fixed" version that I have (still<br>
has the zorder bug...) as soon as I get accepted. Other than that thing,<br>
it's all working for me. Final note, I'm new to ruby, so I apologize if<br>
there are memory problems.. memory bugs were the hardest for me to grasp<br>
and understand in c++ - and i really haven't even looked at how ruby<br>
handles memory yet (erm... my bad), and if there's a way to call<br>
"delete" on c++ pointers passed down to ruby scripts, or if that's even<br>
needed.<br>
(Say I remove an item from a qt list, the qt list has removeAt or<br>
something like that which returns the still active pointer to the item<br>
that it removed from the list and must be deleted manually, not sure<br>
what to do in ruby if anything...)<br>
new version also has the slier</blockquote>All C++ lists are converted to Ruby Arrays and so there is no equivalent of 'destroy on remove' - the underlying C++ instances for the list elements will be deleted when Ruby GCs them. If a list element was created in the C++ world, it won't be deleted though as the qtruby runtime assumes that the C++ side will delete.<br>
<br>-- Richard<br></div><br>