Anobium

Hello, Can you share more information? Operating system? Screenshots? Code. Thanks

Excellent. I will commit to the release. There will be a release very soon that will include these changes. There may/will be other issues like this. We can change the toolchain, I just need the time to do it. :-)

How about ? GCBASIC (2026.04.26 (Windows 64 bit) : Build 1573) Compiling: blinker_minimal.gcb Program compiled successfully (Compile time: 1.5 seconds) Summary: Compiled: Program lines: 6 Subroutines: User: 0 ; System: 2 of 485 ; Total: 2 Chip resource usage: Program Memory: 36/4096 words (.88%) RAM: 0/512 bytes (0%) OSC: 1Mhz Assembling program using GCASM Program assembled successfully (Assembly time: 0 seconds) Code Segment: 64/4096 words (1.56%) Done

Great. Check the properties of the application..are they set to maximise on open. But, all good changes.

This is what I recommend. This is real and not a mock up. Note the hex allocation comes from GCASM or AVRASM2, so this ( correctly ) is shown in the GCASM section. And, if using AVRASM2 then there will be nothing shown as this information in the LST file produced by AVRASM2. This shows the real extent of the progmem used. Evan GCBASIC (2026.04.23 (Windows 64 bit) : Build 1573) Compiling: blinker_minimal.gcb Program compiled successfully (Compile time: 1.5 seconds) Summary: Compiled: Program lines:...

This is what I recommend. This is real and not a mock up. Note the hex allocation comes from GCASM or AVRASM2, so this ( correctly ) is shown in the GCASM section. And, if using AVRASM2 then there will be nothing shown as this information in the LST file produced by AVRASM2. This shows the real extent of the progmem used. Evan GCBASIC (2026.04.23 (Windows 64 bit) : Build 1571) Compiling: blinker_minimal.gcb Program compiled successfully (Compile time: 1.5 seconds) Summary: Compiled: Program lines:...

Before I made any changes. I changed the Assember from GCASM to AVR2ASM ( you easily do the same ). It reports the memory usages as 114 bytes - which is correct based on my previous analysis. "ATtiny841" memory use summary [bytes]: Segment Begin End Code Data Used Size Use% .cseg 0x000000 0x000080 114 0 114 8192 1.4% This show the information is a clear way. Does this help the best way to show?

Please download and replace the existing Programmer Editor.exe from https://1drv.ms/u/c/2f87ffe77f3dbec7/IQCjuayRtj9LQZ6GrN5HcTIZAcyIs8u9GfUB8vRGB-L4cHc?e=uZAA5U Hopefully, this resolves. Here's the changelog document. It covers all 14 changes made from v4.01 to v4.02 File header & version number Form border, resize and window control behaviour DPI/4K scaling fix MinimumSize recalculation for Add/Edit/Delete visibility OK & Cancel button centring New Reset Size button and its click handler