What is the correct way to get wxPanel visible size?

[Tapsa]

I have two wxPanels, whose visible width and height I need to get, but both GetSize() and GetClientSize() return false sizes.
GetSize() from wxBufferedPaintDC also returns false size. I want to center my wxBitmap to the wxPanel, but without real sizes that's impossible.
I have not made any scaling for these wxPanels yet. GetClippingBox() also does not work, returns impossible sizes for the visible area size.

[doublemax]

I have two wxPanels, whose visible width and height I need to get, but both GetSize() and GetClientSize() return false sizes.

That's almost impossible. The only reason i could think of is that you connected the paint event handler to a method of the parent frame incorrectly and get the size of the parent frame instead.

Can you show some code?

[Tapsa]

I do connect the paint event to wxFrame using this:

Code: Select all

Graphics_SLP_Image->Connect(Graphics_SLP_Image->GetId(), wxEVT_PAINT, wxPaintEventHandler(AGE_Frame::OnDrawGraphicSLP), NULL, this);

"this" is the wxFrame.

[T-Rex]

As far as I understand, you can try to get wxClientDC and it's size when you want, not only in wxEVT_PAINT handler. So, possibly, the wxClientDC's getSize() should do what you want.

[doublemax]

Code: Select all

Graphics_SLP_Image->Connect(Graphics_SLP_Image->GetId(), wxEVT_PAINT, wxPaintEventHandler(AGE_Frame::OnDrawGraphicSLP), NULL, this);

This is correct, but then GetSize() and GetClientSize() in the paint event handler will return the values for the frame. Use Graphics_SLP_Image->GetClientSize() instead.

This kind of code is cleaner if you keep the paint event handler in the panel class.

[Tapsa]

I'm sorry to say, but I tried your suggestions before I came here to ask this. I think there is something else broken. wxWidgets basically allows my GUI code to result in broken behavior, without telling me where the error is.

[PB]

If you want to get help you need to provide necessary information, as usual starting with wxWidgets version and the platform used. Then provide the minimum compilable example to demonstrate the issue. It could also be useful not just saying "false sizes" but to provide hard numbers for expected and returned sizes, so people may have a better idea about what is going on.

[Tapsa]

It's okay. Instead of taking 1 hour to make minimal sample, I will move my graphics view to separate window, which seems better for my use.

If you want to fix wxWidgets issues you should compile my program and even try to port it to wxWidgets 3.0.2 from 2.8.12. There are so many issues (when upgrading to 3) it would take days to make minimal samples for all of them.
https://github.com/Tapsa/AGE

In this particular case my wxPanel has size around 300 x 300 pixels, but it returns size that is 3 to 4 times larger than that. This must also be the reason why wxWrapSizer fails to work in my wxScrolledWindow (size around 700 x 600).

[PB]

It's okay. Instead of taking 1 hour to make minimal sample, I will move my graphics view to separate window, which seems better for my use.

Sorry, to create a truly useful minimal example of the issue described in the OP should take just a few minutes and nobody is going to do that for you.

If you want to fix wxWidgets issues you should compile my program and even try to port it to wxWidgets 3.0.2 from 2.8.12. There are so many issues (when upgrading to 3) it would take days to make minimal samples for all of them.

I'm afraid you are under wrong impression here. Firstly, you should prove the issue is within wxWidgets using approach described above. Secondly, wxWidgets is a community project rather dependent on submissions from people using it, who do it for free. Lastly, if you want someone to port your application and fix the tons of bugs you admit it has, you will have to pay them or find something else to motivate them..

[Tapsa]

Which is why we can let this case rest in peace. I can not do a minimal sample of this within minutes.
Obviously it is not necessarily an error withing wxWidgets, but rather I have been using wxWidgets in a way that was never meant to be.