- Welcome to Pelles C forum.
Pelles C forum
News:
Download Pelles C here: http://www.smorgasbordet.com/pellesc/
Recent posts
#11
Tips & tricks / Windows API tutorial for FreeB...
Last post by Vortex - August 31, 2025, 11:19:42 AMThe tutorial set originally designed for FreeBASIC could be useful for Win32API programming with Pelles C :
https://www.freebasic.net/forum/viewtopic.php?p=308895#p308895
The tutorials by Vanya :
https://users.freebasic-portal.de/freebasicru/api.html
Quotevvanag, this is Vanya's Windows API tutorial for FreeBASIC: https://users.freebasic-portal.de/freebasicru/book.html. It is written in Russian, but there is a button for translation into many languages, select "English". From the menu select "Articles" ---> "FreeBASIC + API (series of articles)". Very helpful!
https://www.freebasic.net/forum/viewtopic.php?p=308895#p308895
The tutorials by Vanya :
https://users.freebasic-portal.de/freebasicru/api.html
#12
General discussions / Re: Older version that run on ...
Last post by WiiLF23 - August 27, 2025, 03:54:16 AMYou should indicate whether your inquiring about NT 5.1 (XP) IDE support or the C compiler binary itself, as many use Notepad++ and CLI the build process via hotkey configuration. Bypasses all of the bugs and occasional memory violation issues Pelles C (latest) sometimes produces, while rendering LOC's much faster (and dark-mode is very nice).
As the source is closed, it is anyone's guess. Or alternatively, build on Vista+ and target NT 5.1 in your build config in Pelles C project settings, which absolutely will run on XP (32-bit) no problem. Its the API changes that your "mature" codebase will melt down upon if targeting Vista+ and expecting "XP out of the box support" for example, at a later date.
Best to consider early OS support from day 1 and maintain as the code grows.
Maybe this is bidirectionally confusing in regards the first post.
As the source is closed, it is anyone's guess. Or alternatively, build on Vista+ and target NT 5.1 in your build config in Pelles C project settings, which absolutely will run on XP (32-bit) no problem. Its the API changes that your "mature" codebase will melt down upon if targeting Vista+ and expecting "XP out of the box support" for example, at a later date.
Best to consider early OS support from day 1 and maintain as the code grows.
Maybe this is bidirectionally confusing in regards the first post.
#13
Bug reports / Re: Debugging code that calls ...
Last post by MrBcx - August 21, 2025, 04:01:04 PMBefore I retired, there were several times when our IT Dept's security measures completely
brought our engineering software to a halt. I'm talking about professional software that
we spent tens of thousands of dollars annually licensing. When that software stopped working,
my staff stopped working, and it fell to me to work with our IT guys to get things restored.
Typically, the IT staff could create a group policy that exempted my staff from certain
enterprise level security measures that were running and thus allowed our software to return
to business. But it was always a fire drill when our software suddenly stopped working.
brought our engineering software to a halt. I'm talking about professional software that
we spent tens of thousands of dollars annually licensing. When that software stopped working,
my staff stopped working, and it fell to me to work with our IT guys to get things restored.
Typically, the IT staff could create a group policy that exempted my staff from certain
enterprise level security measures that were running and thus allowed our software to return
to business. But it was always a fire drill when our software suddenly stopped working.
#14
Bug reports / Re: Debugging code that calls ...
Last post by Vortex - August 21, 2025, 07:59:05 AMHi DMac,
On the command prompt, you can view the group policies with :
This can give a clue about the security measures.
On the command prompt, you can view the group policies with :
Code Select
gpresult /zThis can give a clue about the security measures.
#15
Bug reports / Re: Debugging code that calls ...
Last post by DMac - August 21, 2025, 06:10:44 AMI loaded v13 on my home laptop running Windows 10 pro x64 22H2, and launched the example project building both x86 and x64 and had no issues launching the open file dialog in debug mode.
I'm now inclined to think that the various security configurations the IT department employs must be interfering with the open file dialog call from debug mode. Not only this but it caused the save file dialog to malfunction in another application on that machine after running the test project. This necessitated a reboot to restore functionality.
Even though both my home and work machine share the same OS and build, the home machine seems to be more stable generally.
In light of this I guess it is safe to say this is not actually a Pelles C Bug.👍
I'm now inclined to think that the various security configurations the IT department employs must be interfering with the open file dialog call from debug mode. Not only this but it caused the save file dialog to malfunction in another application on that machine after running the test project. This necessitated a reboot to restore functionality.
Even though both my home and work machine share the same OS and build, the home machine seems to be more stable generally.
In light of this I guess it is safe to say this is not actually a Pelles C Bug.👍
#16
Bug reports / Re: Debugging code that calls ...
Last post by John Z - August 20, 2025, 12:07:57 AMTimo's finding is confirmed in Win 23H2 .
Running without debug one can click the Open File Dialog button as many times as wanted. Running under debug issues start to show up on the second click of the Open File Dialog button. I needed to do a break on the debug menu then hit Go/Debug button again to get access to the dialog.
John Z
Running without debug one can click the Open File Dialog button as many times as wanted. Running under debug issues start to show up on the second click of the Open File Dialog button. I needed to do a break on the debug menu then hit Go/Debug button again to get access to the dialog.
John Z
#17
Tips & tricks / Re: Useful website for WIndows...
Last post by Vortex - August 19, 2025, 08:58:02 PM #18
Bug reports / Re: Debugging code that calls ...
Last post by TimoVJL - August 19, 2025, 05:21:22 AMExample works normally in Window 10 x64 22H2
In same session, second time to open file dialog have to activate debug window and from Debug -> Break to get dialog visible.
In same session, second time to open file dialog have to activate debug window and from Debug -> Break to get dialog visible.
#19
Bug reports / Re: Debugging code that calls ...
Last post by John Z - August 19, 2025, 02:32:08 AMHi DMac,
Yes very strange - same .exe run on different systems . . . . drastically different results.
Could it be an antivirus tool doing something, I wonder. At a loss for now since I can't reproduce
and
I only have one laptop with me - of course ....
Maybe Timo can try the .exe's I posted too.
John Z
Yes very strange - same .exe run on different systems . . . . drastically different results.
Could it be an antivirus tool doing something, I wonder. At a loss for now since I can't reproduce
andI only have one laptop with me - of course ....
Maybe Timo can try the .exe's I posted too.
John Z
#20
Bug reports / Re: Debugging code that calls ...
Last post by DMac - August 19, 2025, 01:27:26 AMHi John,
I tried the project you attached.
I get the same strange behavior. I have screen captured an internal debugger error which might provide some clues. I also provide a screenshot of the file browser dialog when it hangs.
When this happens I have to reboot the machine to get the dialog working again.
I think I'll forego trying to debug this on the work laptop going forward.
I tried the project you attached.
I get the same strange behavior. I have screen captured an internal debugger error which might provide some clues. I also provide a screenshot of the file browser dialog when it hangs.
When this happens I have to reboot the machine to get the dialog working again.
I think I'll forego trying to debug this on the work laptop going forward.