41
Using Code::Blocks / Re: Using a file dialog with wxSmith?
« Last post by Commaster on November 27, 2023, 07:47:11 am »I hope this helps https://docs.wxwidgets.org/3.2/classwx_file_dialog.html
News:
As usual while waiting for the next release - don't forget to check the nightly builds in the forum.
Recent Posts
42
Using Code::Blocks / Using a file dialog with wxSmith?
« Last post by Sephiroth on November 27, 2023, 12:36:00 am »I'm new to wxSmith so this is probably me missing something, but I need some guidance. I've got a basic app laid out and working, but now I need to be able to open and save files. In Windows (and X) I had an "OpenFileDialog" I could use. I assume wxWidgets has one of these but I am not sure how to find it. I've got a menu entry setup and functioning for bringing up said dialog, but where is it? How can I get an OFD to open a file so I can read or edit it?
43
Help / Re: Trying to get wxWidgets 3.2 to work with CB...
« Last post by Sephiroth on November 27, 2023, 12:31:52 am »I just wanted to report back that I am good. Updating the wizard from the repository that was linked above fixed everything. I can now create wxWidgets apps and use wxSmith without a hitch. Thank you!
44
General (but related to Code::Blocks) / Re: C::B as a Win 3.11/95/DOS development workhorse
« Last post by adalbert on November 26, 2023, 08:02:39 pm »@adalbert Great video. You can only clarify - did you edit everything yourself and make scripts for the demonstration, or is your video based on other people's video materials, and you just edited it and voiced it?
Thanks! I did everything from scratch, the technical side (whole installation script, C++ sample apps, build scripts, config files etc) and the video. I was working on it for around a year step by step with really long breaks. Finding working compilers and proper versions of libraries for old platforms was probably the most time consuming part. All files that I prepared are available in the linked GitHub repository. I may even need to divide it into different repositories because there is a lot off stuff going on, e.g. the "launch in emulated Windows 3.11" thing can be used independently of CodeBlocks. And each step probably could benefit from additional documentation.
It started when I wanted to make a simple drag-n-drop file transfer app which would work between new and legacy machines (still didn't polish it to the stage where I could publish the code, but that's what you see on the old laptop and the new Mac), I used an ancient version of C++ Builder first, but then I wanted to use more recent tools and have cross platform capabilities. And code completion, etc. So C::B and wxWidgets worked pretty well here, by providing the same RAD-style experience after setting everything up properly.
45
General (but related to Code::Blocks) / Re: C::B as a Win 3.11/95/DOS development workhorse
« Last post by omlk on November 26, 2023, 07:55:05 pm »@adalbert Great video. You can only clarify - did you edit everything yourself and make scripts for the demonstration, or is your video based on other people's video materials, and you just edited it and voiced it?
46
General (but related to Code::Blocks) / C::B as a Win 3.11/95/DOS development workhorse
« Last post by adalbert on November 26, 2023, 03:07:52 pm »I made a bunch of installation batch scripts and config files, which can be used to automatically install Code::Blocks with... Windows 3.11/95 integration (via DOSBox-X, with mouse and network integration), so you can automatically build and execute an application directly in Windows 3.11 / 95 / DOS. Win 3.11 / 95 is installed in emulated hard drive from your own installation files via automated installation script.
I also adjusted wxWidgets 2.8.12 to work with Win 3.11/Win32s and wxWidgets 3.0.5 to work under Windows 95.
A set of compilers for various build targets is downloaded, installed and automatically configured inside C::B.
Everything uses relative file paths, so you can just launch C::B and start building apps for legacy systems without manually setting up anything. I adjusted wxWidgets templates so you can select Win 3.11 / 95 target and it selects a compiler and configures app execution automatically.
I know this is weird and eccentric, but maybe someone will find a use for it. You start the installation process via SetupCodeBlocks_AllInOne.bat script.
Repository: https://github.com/adbrt/cb-legacy-dev
Video overview/tutorial: https://youtu.be/d6L272OApVg
I also adjusted wxWidgets 2.8.12 to work with Win 3.11/Win32s and wxWidgets 3.0.5 to work under Windows 95.
A set of compilers for various build targets is downloaded, installed and automatically configured inside C::B.
Everything uses relative file paths, so you can just launch C::B and start building apps for legacy systems without manually setting up anything. I adjusted wxWidgets templates so you can select Win 3.11 / 95 target and it selects a compiler and configures app execution automatically.
I know this is weird and eccentric, but maybe someone will find a use for it. You start the installation process via SetupCodeBlocks_AllInOne.bat script.
Repository: https://github.com/adbrt/cb-legacy-dev
Video overview/tutorial: https://youtu.be/d6L272OApVg
47
Development / Re: C::B dark mode in Windows
« Last post by adalbert on November 26, 2023, 02:44:22 pm »OK, I uploaded the code/build files and binaries to GitHub.
https://github.com/adbrt/codeblocks-dark-mode-msw/releases/tag/release
https://github.com/adbrt/codeblocks-dark-mode-msw
Currently I just wanted to create a working proof of concept, so the dark mode is hardcoded using MSWEnableDarkMode(), I adjusted lexers XML files to have dark mode by defauld and also added a default.conf file which changes additional colors (this is necessary to change ie. the caret color). You need to run it using CbLauncher.exe so the default.conf file gets loaded from the app directory.
To make everything proper, a toggle switch for light/dark mode, automatic theme switching etc. would need to be added. But that will require more time.
Also, not only background/foreground of code editor needs to be adjusted, colours of text need to be adjusted individually for normal and dark mode, so it is readable and looks good.
https://github.com/adbrt/codeblocks-dark-mode-msw/releases/tag/release
https://github.com/adbrt/codeblocks-dark-mode-msw
Currently I just wanted to create a working proof of concept, so the dark mode is hardcoded using MSWEnableDarkMode(), I adjusted lexers XML files to have dark mode by defauld and also added a default.conf file which changes additional colors (this is necessary to change ie. the caret color). You need to run it using CbLauncher.exe so the default.conf file gets loaded from the app directory.
To make everything proper, a toggle switch for light/dark mode, automatic theme switching etc. would need to be added. But that will require more time.
Also, not only background/foreground of code editor needs to be adjusted, colours of text need to be adjusted individually for normal and dark mode, so it is readable and looks good.
can you use any color in the color palette instead of the black interface, for example?Probably not, at least not without going really deep into the wxWidgets/CodeBlocks code, the dark interface colours are probably hardcoded somewhere, or maybe even hardcoded in the Windows itself
48
Help / Re: Where the code of the tooltip generate and call wxWidgets render?
« Last post by Wkerry on November 26, 2023, 12:25:46 am »Most IDE's you change variables via the watch variable/structure feature. Have you look there? I have not had to modify a variable while a program is running.
49
Help / Where the code of the tooltip generate and call wxWidgets render?
« Last post by omlk on November 25, 2023, 06:50:52 pm »Who knows where the formation of the tooltip takes place, if you press CTRL, the debugger pauses in the drop-down form of the value of the variable? I found I want to change the form(tooltip) view, how and where it should be done, because looking at the code, it seems that it is a spaghetti of c++ classes and interfaces, imitations, etc., and also scattered in different files somehow. Horror.
tooltip_gdb.png (225.34 kB, 1280x1024)
tooltip_gdb2.PNG (240.15 kB, 1279x1023)
Code
\trunk\src\sdk\cbplugin.cpp ~row:953-99450
Help / Re: Trying to get wxWidgets 3.2 to work with CB...
« Last post by Sephiroth on November 25, 2023, 04:50:03 pm »The wizard looks if "$(#wx)/include/wx/wx.h" exists, check if your wx vaiable points to the correct folder (where include and lib reside).I did add that, but did not post about it. I have the include folder searchable also.
BTW, you must add "$(#wx.INCLUDE)" to the compiler search path.