wxWidgets Discussion Forum

Yes, it does work, I get the behaviour I want. Except I wasn't sure whether I was collecting some "free floating bindings" somewhere that in the long run would add up, perhaps slowing down my app or create a memory leak. I didn't find anything in the documentation about that, if a wx-destr...

In my application, I can create new modules during runtime. A module is an internal application data class, nothing to do with wxWidgets. Each time a new module is created, a wxToggleButton appears on a panel, added to a sizer on that panel. Because I don't know how many buttons will be present duri...

wxTextCtrl comes with built-in hotkeys, such as Ctrl+x, Ctrl+c and Ctrl+v for cut, copy and paste resp. There are others too, such as Ctrl+a for select all. I would like to implement additional hotkeys without interfering with the existing ones. Is there somewhere an exhaustive list of all the alrea...

Yes, it was only until I started writing my own conversion function that I started noticing the sensitivity to the format of the char. By default, a 'char' is a 'signed char' and thus has only 7 bits of data plus a sign bit. This screws up the conversion of course (although I'm not sure why 0xA0 and...

I have this curious problem when trying to display something in hex code. First I make a string with 256 characters, in which each character has another number (it's just a loop of increasing numbers) wxString NumTestString; char TempChar = 0x00; for (int Counter = 0; Counter < 256; Counter++) { Num...

That could work but you can only access a member of an actual object, not of the class. So somewhere in your code, you'll probably create an instance of MyFrame, let's call it MyFrameObject, e.g. : // in a header file called MyApp.h for the sake of this explanation MyFrame *MyFrameObject; // then in...

I have been struggling with wxDatePickerCtrl and wxTimePickerCtrl a bit myself too. Both have a data exchange format using wxDateTime, however - in case of wxDatePickerCtrl, the time part is "ignored" - in case of wxTimePickerCtrl, the date part is "ignored" however the "unu...

Thanks guys, but it seems there's no answer to my original question "is there a pre-defined constant for the minimum and maximum allowed wxDateTime" Therefore I defined some myself, in accordance with the minimum and maximum expected in my application. #define IMR_MAX_DATETIME wxDateTime(1...

If I want to determine the minimum and maximum of a collection of numbers, typically I do something like the following : int Min = INT_MAX; // INT_MAX is defined in limits.h as 2147483647 int Max = INT_MIN; // INT_MIN is defined in limits.h as (-INT_MAX-1) //in a loop, fetching NewNumber each time ....

Here's an observation I didn't find anywhere on the net, and which took me quite some time and frustration to find out. In my application, I want to log data from a serial port. wxTextCtrl looked like a good idea to me because the logging happens in textual format anyway, I can use it also for other...

Ah, I see, that was the missing piece of the puzzle, all clear now.
Thanks for the clarifications.

I am familiar with parenting and using the this-parameter in this context, although I have to admit I didn't consider it yet in this discussion. Refering again to the first example (BlankwxSmithFrame), that can indeed explain the status bar. StatusBar1 = new wxStatusBar(this, ID_STATUSBAR1, 0, _T(&q...

But in wxWidgets it often happens that another object takes ownership of that pointer and the memory will be deleted internally. Aha, that's what I started to suspect indeed, there's some underlying code/mechanism copying pointers or as you say "taking ownership". Ok, I won't break my hea...

Ah yes, but my problem is this (refering to the first example with "wxSmith" now) : The pointer, e.g. wxMenu* Menu1 is declared only in the constructor, which as far as I know behaves as any other function. Next, some memory is allocated with the new-operator. This will indeed allocate the...

Ah yes, good spot, it's the opposite of course, new-operations are on the heap indeed. Here's two different examples of (an extract of) auto-generated code by the Code::Blocks wizard of a blank project (just used the wizard, no other code added by me) First one is when choosing the option to use wxS...