wxWidgets Discussion Forum

Utensil wrote:
一个人如果协助了别人得到1分，如果真的帮助到别人得到5分，有了这样清楚明白的给分规则，别人一看你的wxAward点数，就可以大约了解你帮助别人的程度，这比由提问者随意指定悬赏分要好。

我个人希望，wxAward系统更多是一种娱乐，更多是一种意思意思：提问者用以表达谢意，回答者获得一种精神上的满足——我的回答帮到忙了、被接受了。

Hi, Utensil.
支持!!!

Hi.
Please try to use wxGrid::IsInSelection to check whether the cell is selected. So you need go through all cells.

It seems a bug of wx, at least in wx 2.6.2.

OK, roxaz. Could you just do the following steps again? 1) New a Win32 Project(Empty Project). 2) Just add a single source file, called main.cpp. 3) Paste your demo code into it. 4) Change project configuration a) Add additional "Include" paths b) Add additional "Libs" paths c) Specify libs: comctl3...

Hi, michel. Your code is quite clear, and I've read and compiled it on my machine. But I think the behavior is reasonable. When I am editing a cell, I click the button. I think the mouse event will be sent to that cell editor. So then the editor hide. And if you click the "Close" button again, the m...

Hi, roxaz.
Could you just post your wx lib's project configuration?

* Code Gneration: Multi-threaded Debug DLL (/MDd)

Please try to use "Multi-threaded Debug (/MTd)" to build your code again.

It seems that your wx libs are built in static way.

如果你的文字是位图的话,我觉得你也可以这样做.
1) 可能要重新写OnPaint()(可以自己写个新的Handler, 专门去管理EVT_PAINT事件).
2) 定时器是一定要用了吧.
2) 位图读到一个wxMemoryDC里. 最后再用wxDC::Blit,把位图的DC帖到BUTTON的DC上. 因为存在前后的拼接, Blit可能要用两次.

以上意见, 仅供参考.

Hi, ruvindra.

The parent window will help you to destroy all its child windows. So it's unnecessary for you to do that by yourself in most cases.

PS: use "delete" is not good, it's better to call destroy() if you really want to do that by your own.

Regards.

Do you mean you click the button during you are editing the cell?

It's better to post your code maybe.

Hi. Maybe I am not sure I understand what is your problem. I think maybe you can try the dynamic handlers, Connect and Disconnect or PushEventHandler() and PopEventHandler. So before you call Select() you can disconnect or pop the handler, and after the call, you can re-connect and push the handler....

There is a very useful tools on Code Project for you. It's called "Visual Leak Detector". The link is http://www.codeproject.com/KB/applicati ... ctor.aspx..

It will help to find where the memeory leak is.

Wish it can help you!!

Regards.

Yes, David.

After traced the code of wx, I found the situation like what you said. There is a wxYield() in a executing-path in OnA. wxYield will get the next event and process it. So OnB() will be called in OnA(). That's the problem!

Thanks again, guys!! I've learned much from this ticket.

2.8时代最后一个版本了.

Thanks, mc2r and megabyte.

I think I should write some sample to test.

Dear all, Recentlly I met a confusing problem about wx event handling mechanism. I will try my best to describe it. Assumed there are two event A and B, and OnA() and OnB() are their handlers respective, event A is the first event, and B is the second. So OnA() will be called first, but it will take...