Known Bugs...

[Dabzy]

Known Bugs

1) wxTextCtrl Locking

If say, you open the Menu->File->New Project dialog, which has a number of text boxes inside of it, once you go into a text box, place text in it, then click out of it (Be it another textbox or whatever), that's it, you cannot access that text box again via a click of the mouse. After further inspection, you can tab around the text boxs back to text boxs that have shut up shop once data is entered into them, and then type text in again, but, the caret doesnt follow if you get me, instead, the caret stays in the last text box that was focused, and dances about as if it was in the textbox where your entering data... It's another odd thing that has cropped up. Dunno whats happened there, I originally thought I was missing a event.Skip() statement somewhere, but I cannot see where. It's funny though, because trying to implement a fudge, there are a few events not hitting, like keyboard and mouse events. I've discussed it with a couple of peeps in the wxWidgets IRC channel, one of them said does wxEVT_COMMAND_TEXT_ENTER work when handling events... Which it does, further inspection shows the wxEVT_COMMAND_TEXT_UPDATED event is handled as expected as well. After trying everything, and sending them the whole lot to take a peek... They are none the wiser because, well, it should work within their reasonings. Their only recommendation is to upgrade, and use a new[ish] Bind() function for connecting events to handlers, this is the actual offical recommendation, ahem, DO NOT USE CONNECT().
Buggering hells bollocks!
So, with that, as it stands, lol, I've got it where if you hit the return key after adding stuff to the text box, or any text boxes in Launchpad, you can get back into them with the mouse, tabbing out or clicking another control will render it locked up unless you do the tabbing around the doors trick mentioned above! Eeeeee eh, never a dull day! In all seriousness... Moving it to a new version may just be the idea, if any porting path is under taken, I'll probably move the project over to C++, at least then, when needing help or looking for answers, it'll be easier to get it as I'm not based on a "library within a library" setup like I am now. It is what it is, not a show stopper, there is an answer, but I cannot see it, and neither can others who know wxWidgets inside out, cut a long story short... I haven't got a fooking clue what I've done to cause that effect! teehehehe

Dabzy