New:Change Preferences Editor position and movement controls.
New: Improved program calculation size via RecalcSubSizes(), and change variable types to prevent overflow.
I did spot another issue... I took the blinker_mininal.gcb soruce and made it big, ( copied and copied) until the compiler said it would not fit the Program Memory... then, i deleted enough to make it compiler. When I loaded into AVRDude... it was not 99.99% !! The Problem On AVR targets, the compiler's reported Program Memory usage was significantly higher than the actual flash consumed. For example, compiling for an ATtiny841 (4096 words): Program Memory: 4026/4096 words (98.29%) ← compiler (wrong)...
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:...