Activity for pecan
-
pecan modified a comment on ticket #1591
Fixed svn 13832. Garbage in unintialized variable causing the first mouse right-click to be interpreted as a mouse drag. A missing event.Skip() was causing the request for context popups to be ignored (Linux). On high DPI monitors some mouse right clicks were missed because mouse jitter was being interpreted as a beginning drag.
-
Fixed svn 13832. Garbage in unintialized variable cause the first mouse right-click to be interpreted as a mouse drag. A missing event.Skip() was causing the request for context popups to be ignored (Linux). On high DPI monitors some mouse right clicks were missed because mouse jitter was being interpreted as a beginning drag.
-
Right clic does not work the 1st time in the managment window
-
Fixed svn 13832. Garbage in unintialized variable cause the first mouse right-click to be interpreted as a mouse drag. An missing event.Skip() was causing the request for context popups to be ignored (Linux). On high DPI monitors some mouse right clicks were missed because mouse jitter was being interpreted as a beginning drag.
-
* DragScroll: Fix missed first Manager mouse Right click.
-
Thanks for the help chasing this down guys. The cause appears to be (not a missing event.Skip()), but an uninitialized boolean variable that had an int(30) in it. After the first right-click in the management tree, the var got it's first true/false value resulting in correct performance. That would also explain why the difference in compilers would provoke or hide the problem. While I'm here, some changes for high DPI need examination. I'll work with this for awhile to make sure I'm not "halluci...
-
Thanks for the help chasing this down guys. The cause appears to be (not a missing event.Skip()), but an uninitialized boolean variable that had an int(30) in it. After the first right-click in the management tree, the var got it's first true/false value resulting correct performance. That would also explain why the difference in compilers would provoke or hide the problem. I'll work with this for awhile to make sure I'm not "hallucinating".
-
Thanks for the help chasing this down guys. The cause appears to be (not a missing event.Skip()), but an uninitialized boolean variable that had an int(30) in it. After the first right-click in the management tree, the var got it's first true/false value resulting correct performance. I'll work with this for awhile to make sure I'm not "hallucinating".
-
Thanks for the help chasing this down guys. The cause appears to be (not a missing event.Skip()), but an uninitialized boolean variable that had an int(30) in it. After the first right-click in the management tree, the var got it's first value resulting correct performance. I'll work with this for awhile to make sure I'm not "hallucinating".
-
I've also experienced this problem. (Windows 11; CB svn 13831; wx328). Could those having the disappearing mouse right-click problem please list the plugins they are using along with the plugins version. This problem is usually caused by a missing "event.Skip();" statement in a plugin event. A list of plugins to inspect would be very useful.
-
I've also experienced this problem. (Windows 11; CB svn 13831; wx328). Could those having the diappearing mouse right-click problem please list the plugins they are using along with the plugins version. This problem is usually caused by a missing "event.Skip();" statement in a plugin event. A list of plugins to inspect would be very useful.
-
I've also experienced this problem. (Windows 11; CB svn 13831; wx328). Could those having the diappearing mouse right-click problem please list the plugins they are using along with the plugins version. This problem is usually caused by a missing "event.Skip();" statement in a plugin event. A list of plugin to inspect would be very useful.
-
- codesnippets: Don't open duplicate temporary .txt files. Fix crash possibility.
-
clangd_client: support versioned executable auto detection
-
Thanks Applied SVN rev 13830
-
* clangd_client: Apply ticket 1593 - Auto detect versioned clangd executable (Thanks Christo)
-
Prompt to Gemini AI: For CodeBlocks, what does a contributor mean by ticket 1593 when he states: Installing clangd from https://apt.llvm.org/ results in verisioned libraries, for eg. /usr/bin/clangd-20 in my recent installation. Attached patch helps to autodetect this. With patch code: ticket 1593 Gemini said In Code::Blocks ticket 1593, the contributor is addressing a common issue where the IDE fails to find the clangd executable (the Language Server Protocol provider) because the filename isn't...
-
Prompt to Gemini AI: For CodeBlocks, what does a contributor mean by ticket 1593 when he states: Installing clangd from https://apt.llvm.org/ results in verisioned libraries, for eg. /usr/bin/clangd-20 in my recent installation. Attached patch helps to autodetect this. With patch code: ticket 1593 Gemini said In Code::Blocks ticket 1593, the contributor is addressing a common issue where the IDE fails to find the clangd executable (the Language Server Protocol provider) because the filename isn't...
-
clangd_client: add option to parse only opened files
-
Great addition, thanks ! I'll be using this even on a new powerful laptop. Applied SVN rev 13829
-
Great addition, thanks ! I'll be using this even on a new powerful laptop. Applied SVN rev 18829
-
I Posted to wrong ticket.
-
Thanks, great addition ! Applied svn rev 13829
-
* clangd_client: Apply ticket 1592 parse only open files option (thanks Christo)
-
clangd_client: add option to parse only opened files
-
clangd_client: support versioned executable auto detection
-
There are some key bindings that the Keyboard plugin cannot screw around with. Some of those bindings include the Ctrl-C, Ctrl-V, and any key that is hardcoded globally by CodeBlocks itself. One of those hard coded keys is the global binding Ctrl+Tab. It's hard coded into the global accelerator table during start-up and has special programming for Linux and Windows. Since it is already a global key binding, when the plugin asks for the parent menu item, CodeBlocks returns an empty string for good...
-
There are some key bindings that the Keyboard plugin cannot screw around with. Some of those bindings include the Ctrl-C, Ctrl-V, and any key that is hardcoded globally by CodeBlocks itself. One of those hard coded keys is the global binding Ctrl+Tab. It's hard coded into the global accelerator table during start-up and has special programming for Linux and Windows. Since it is already a global key binding, when the plugin asks for the parent menu item, CodeBlocks returns an empty string for good...
-
There are some key bindings that the Keyboard plugin cannot screw around with. Some of those bindings include the Ctrl-C, Ctrl-V, and any key that is hardcoded globally by CodeBlocks itself. One of those hard coded keys is the global binding Ctrl+Tab. It's hard coded into the global accelerator table during start-up and has special programming for Linux and Windows. Since it is already a global key binding, when the plugin asks for the parent menu item, CodeBlocks returns an empty string for good...
-
Multiple keyboard shortcuts not saved properly
-
There are some key bindings that the Keyboard plugin cannot screw around with. Some of those bindings include the Ctrl-C, Ctrl-V, and any key that is hardcoded globally by CodeBlocks itself. One of those hard coded keys is the global binding Ctrl+Tab. It's hard coded into the global accelerator table during start-up and has special programming for Linux and Windows. Since it is already a global key binding, when the plugin asks for the parent menu item, CodeBlocks returns an empty string for good...
-
Multiple keyboard shortcuts not saved properly
-
- clangd_client: cleanup using -Wextra, no functional changes
-
- codesnippets: correct copy .zip error in post build steps
-
removing the FortranProject folder creation from checkout
-
- codesnippets: remove use of $(CODEBLOCKS) CB variable in .cbp for ollydbg
-
- codesnippets: place comment in update32_64.bat
-
- codesnippets: commit missing update files
-
- codesnippets: Add right-click context popups and clean up code
-
Crash in wxRecursionGuard in clangd_client
-
Fixed svn 13797, thanks ollydbg
-
* clangd_client: Fix crash in wxRecursionGuard caused by wrong cross-thread protocol
-
Experimental patch
-
-
Crash in wxRecursionGuard in clangd_client
-
Fix patch 1: Index: src/LSPclient/client.cpp --- src/LSPclient/client.cpp (revision 13794) +++ src/LSPclient/client.cpp (working copy) @@ -1,3 +1,4 @@ +#include <memory> #include <ctime> #include <iomanip> #include <sstream> @@ -938,8 +939,8 @@ void ProcessLanguageClient::OnClangd_stderr(wxThreadEvent& event) // ---------------------------------------------------------------------------- {</sstream></iomanip></ctime></memory> std::string* pErrStr = event.GetPayload<std::string*>();</std::string*>...
-
Crash in wxRecursionGuard in clangd_client
-
Yesterday and today I've run the the following patch with three different debuggers (debugger_gdb, debugger_gdbmi, and debugger_DAP) and they all appear happy: m_grid = new wxPropertyGrid(this, idTooltipGrid, wxDefaultPosition, FromDIP(wxSize(200, 200)), wxPG_SPLITTER_AUTO_CENTER); wxString fontStr = cbDebuggerCommonConfig::GetValueTooltipFont(); //Geimini 2026/02/16 4 lines wxFont font; if (font.SetNativeFontInfo(fontStr)) m_grid->SetFont(font); So, Miguel, if you agree, please format and apply...
-
Gemini 3 is suggesting this change. I'll apply and test for awhile. Any comments about this would be appreciated. ✦ The function cbDebuggerCommonConfig::GetValueTooltipFont() works by retrieving the system's default GUI font, reducing its size by 3 points (with a minimum of 7 points), and returning this smaller font description string unless a custom font is saved in the configuration. The reason the tooltip font appears too big is that this function is not actually used in the ValueTooltip class...
-
Gemini 3 is suggesting this change. I'll apply and test for awhile. Any comments about this would be appreciated. ✦ The function cbDebuggerCommonConfig::GetValueTooltipFont() works by retrieving the system's default GUI font, reducing its size by 3 points (with a minimum of 7 points), and returning this smaller font description string unless a custom font is saved in the configuration. The reason the tooltip font appears too big is that this function is not actually used in the ValueTooltip class...
-
I'll see if Gemini 3 will tell me why the ValueToolTip font is too big.
-
* clangd_client ClassBrowser Fix asserts caused by invalid wxTreeItemId(s)
-
* clangd_client Fix wrong function call in last commit
-
Thanks, My bad. Corrected in rev 13782
-
* clangd_client Move some of ticket 1585 to the correct position (thanks Christo)
-
clangd_client : intermittently hover popup persists after switching editor
-
Applied rev 13781. I now remember that I was peeved that the LSP hover response did not include the URI of the request like other responses. Thanks for the fix
-
* clangd_client: Apply ticket 1585 fixing stuck hover popup (thanks Christo)
-
clangd_client : intermittently hover popup persists after switching editor
-
clangd_client : intermittently hover popup persists after switching editor
-
clangd_client : intermittently hover popup persists after switching editor
-
debuggergdb: kill console with child process
-
Applied rev 13769. Thanks
-
* debuggergdb: kill console with child process (Thanks Sergey Katunin)
-
debuggergdb: kill console with child process
-
Acknowledge. Will test.
-
* watchesdlg.cpp ValueTooltip: Account for new height when adding scrollbar; Avoid wxWidgets property assert when column proportion become less than 1%
-
clangd_client : symbol browser : hang on taking symbol browser when active file out of project
-
Applied rev 13762 Thanks
-
Applied rev 13762 Thanks
-
* Clangd_client - Fix clangd_client_symbol_browser_hang_on_proxy_project. Thanks Christo.
-
BrowseTracker: When jumping back after scrolling away from a jump position, return to that exact position instead of the one before it.
-
Not applied and closed by request of creator
-
clangd_client : symbol browser : hang on taking symbol browser when active file out of project
-
I am not intentionally ignoring this patch. I'm just way behind in the ToDo list after taking care of the responsibilities of old age. :>)
-
* dragscroll: version 1/4/15 251020 Remember the original (current) mouse position for other events to use.
-
* BrowseTracker: Apply JumpTracker.h assert fix (Thanks Christo and Letartare)
-
Enhancements in clangd-client handling of external makefile projects
-
Applied rev 13750 Thanks
-
* Clangd_client: Apply Christo patch #1559 for makefiles (Thanks christo)
-
* DragScroll 1/4/14 25/10/09 Fix using any middle mouse key combo disables context menu.
-
* BrowseTracker 1.4.132 2025/10/01 Apply Christo Patch (Thanks Christo)
-
- BrowseTracker - commit missing images
-
* BrowseTracker: 1.4.131 25/09/17 Apply Christo "Jump to last modified" patch (Thanks Christo)
-
clangd_client : fix crash on completion response after project closed
-
clangd_client : fix crash on completion response after project closed
-
Applied, rev 13734, thanks Christo
-
* Clangd_client: 1.2.142 2025/09/20 Apply Christo 1554 patch and guard like use of pParser. (Thanks Christo)
-
* BrowseTracker: Add missing editor activations to jump tracker array
-
clangd_client : avoid crash when compiler in project file not available
-
Applied rev 13720 Thanks
-
clangd_client : fix crash on reparse
-
Applied rev 13720 Thanks
-
* ClangdClient: Apply patches 1551 and 1552 (Thanks Christo)
-
Small font size in the Disassembly window
-
You should be able to change the font via Settings > Debugger > Value tool tip font.
-
You should be able to change the font size with Settings > Debugger >Value Tooltip Font
-
Bug Report
-
In Settings>Editor>CodeCompletion untick Documentation popup and (just below it) in the Tooltip choiced box select "keyboard only". You can still get the info by using the keyboard shotcuts under edit and view.
-
In Settings>Editor>CodeCompletion untick Documentation popup and (just below it) in the Tooltip choiced box select "keyboard only". You can still get the info by using the keyboard shotcuts under edit and view.
1 >
