Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
Hi, why is nobody of the devs answering to this question?! Do they want to move us to another IDE??

They want you to use the Nightly builds and give feedback and if you use Code Completion try the Clang Code Completion because that was the major holdup on a new release and it might still be the holdup.

Tim S.
2
Help / Re: how do i fix cursor size?
« Last post by Miguel Gimenez on July 19, 2024, 05:20:16 pm »
Cursor size is set in the OS, ask in a forum related to whatever OS you are using.
3
Hi, why is nobody of the devs answering to this question?! Do they want to move us to another IDE??
4
Help / how do i fix cursor size?
« Last post by dominicelliott on July 19, 2024, 09:02:28 am »
Hi everybody,

Please help me how to adjust the cursor size. Thanks!
5
General (but related to Code::Blocks) / Dialog boxes with tab arrows
« Last post by Tinkerer on July 18, 2024, 06:47:23 pm »

Very subtle UI suggestion. 

On dialog boxes with multiple tabs (Global compiler settings)  the tab shifting arrow
do not grey out on the extreme ends.

The Log and Others window has the greying out behaviour.

This only happens when there are many tab and the dialog box is narrow.
6
Note that you can only have one tool running at one time with this config.
I thought you needed just one of the two.

If you need to launch both cmd and ps, you could create a batch file containing this
Code
start powershell
cmd
and use the batch file as the Tool's Executable.
7
Thank you PB

That is good enough for me.

Yes you are right that the Macro is not set yet before a build but that is just fine.

<Movie reference>
"Build it and you can go there"
</Movie reference> ;)

Note that you can only have one tool running at one time with this config.
The the last option may work (detached)  but your have to use it right after a rebuild.

That could work for my workflow.  Rebuild each tool and open the console. Then reuse the consoles while
doing the changes.
8
The only way I can think of now is to add a Tool:

1. Use menu Tools/Configure Tools....
2. Click Add in the User-defined tools dialog.
3. In the Edit Tool dialog use for cmd (without quotes): "Cmd" for Name, "cmd" for Executable and "$(TARGET_OUTPUT_DIR)" for Working directory. Leave Launching options at the first choice.

Unfortunately, macros such as $(TARGET_OUTPUT_DIR) may be working only after a build, so perhaps it would be better to hard-code the path in each tool, even if less convenient.

Now you can launch the tool via Tools menu. You can add another tool for PowerShell in the same way.

Unfortunately, I don't think it is possible to assign a keyboard shortcut for a Tool.

There is probably a better way (e.g., with scripting) but even this may be a bit faster than what are you doing now.
9
Hello All

Is there a direct UI feature that would open a console of my choice (cmd or Powershell) in the debug directory
of the current project.

I am working with code that is written as a console filter (stdin and stdout) with optional command line options.
Think wc or grep in the Unix world.

I need the console open each time I work on this code so I can running them through tests.

For now the shortest way is right click on the source file get the "Project base path" from the properties
switch over to a console  and cd to the pasted path with \bin\Debug added on.

Looking for alternatives

This work is being done on Windows 11.
10
Hello all

I am a 49 veteran of the IT field.  Programmer and Sysadmin, did devops before it had a name,
real time programming, Web application development in the 1.0 era, IT  Management ,
business analyst.

I am in my retirement job of teaching system administration in a community college for over a decade.

Hobby interest is embedded systems.  Tinkering with Arduino, micro-python and retro hardware savaged from the dump.
Learning C for 9th time, fan of Pelles C in another hobby life.

Just Another Prosaic Tinkerer

Pages: [1] 2 3 4 5 6 ... 10