Recent Posts

Pages: 1 2 3 4 5 [6] 7 8 9 10
51
Development / Re: wxSmith use bad constructor for wxStaticBoxSizer
« Last post by Miguel Gimenez on January 12, 2026, 03:59:40 pm »
Fixed in r13767.
52
Help / Re: Incremental Search text box selects itself
« Last post by Miguel Gimenez on January 10, 2026, 02:16:22 pm »
Fixed on Ubuntu, should work also on Debian (commit 13764).
53
Help / Re: Incremental Search text box selects itself
« Last post by Miguel Gimenez on January 10, 2026, 01:45:27 pm »
If you can compile C::B you can try changing this code (in IncrementalSearch.cpp)

Code
#ifdef __WXMAC__
    // on macOS only set focus if we really lost it, to avoid native select all,
    // or it will reset the text selection
    if (!m_pTextCtrl->HasFocus())
        m_pTextCtrl->SetFocus();
#else
    m_pTextCtrl->SetFocus();
#endif

to just

Code
    // only set focus if we really lost it, to avoid native select all
    // or it will reset the text selection
    if (!m_pTextCtrl->HasFocus())
        m_pTextCtrl->SetFocus();
54
Help / Re: Incremental Search text box selects itself
« Last post by sedenion on January 10, 2026, 11:35:49 am »
Hi,

This issue still here in Debian 13 (LMDE 7) Is it an Incremental Search plugin problem or related to WxSmith ? It seem pretty odd that this problem still not addressed since 2022...
55
Development / Re: wxSmith use bad constructor for wxStaticBoxSizer
« Last post by LR83 on January 09, 2026, 10:51:16 am »
The main difficulty lies in the fact that wxStaticBoxSizer is both a sizer and a container. In the current code, wxStaticBoxSizer is classified as a sizer, and there is no category for an object that is both a sizer and a container.
The difficulty lies in finding the owner of the child elements of wxStaticBoxSizer. Currently, it is the parent of the wxStaticBoxSizer that is found, and that is the problem.
The problem is clear, the solution less so!
We will probably need to create a new category and the wxsStaticBoxSizer class will need to inherit from wxsSizer and wxsContainer  :P
56
Development / Re: wxSmith use bad constructor for wxStaticBoxSizer
« Last post by Miguel Gimenez on January 09, 2026, 08:50:49 am »
wxSmith is complex and the original developer is no longer around. I plan to fix this, but I currently have no free time.
57
Not the debug tip window, sometimes, the code completion tip(from the clangd_client plugin) window becomes extremely large, see the blow two screen shot, the tip window cover the whole C::B window, also the tip window extended to another screen.  :(
""
In settings>editor>CodeCompletion what have you got set for "Maximum allowed code completion matches" ?

Hi, sorry for the late reply.
I just looked at my settings, and I see the value is 1000. Is that too big?

I'd say 1000 responses is enough to over fill your screen. 20 to 40 on the screen should be adequate.
58
Not the debug tip window, sometimes, the code completion tip(from the clangd_client plugin) window becomes extremely large, see the blow two screen shot, the tip window cover the whole C::B window, also the tip window extended to another screen.  :(
""
In settings>editor>CodeCompletion what have you got set for "Maximum allowed code completion matches" ?

Hi, sorry for the late reply.
I just looked at my settings, and I see the value is 1000. Is that too big?
59
Scroll bar overlaying problem fixed in rev 13763.
wxPropertyGrid assert fixed in the same rev.

I cannot reproduce the CodeCompletion huge tip size since my
 Settings>Editor>CodeCompletion setting for "Maximum allowed code completion matches" is a reasonable size.
60
I can reproduce the error with wx 3.3.2 on Linux.

The analysers scan-build or cppcheck show several issues with Clangd_client.

Would you care to share those issues with us?
Can you tell us how to reproduce the issue?
Pages: 1 2 3 4 5 [6] 7 8 9 10