#1 · November 25, 2025, 4:19 am

AutoResize Plugin - Effortless Window Resizing for VisualNEO Win

The AutoResize Plugin eliminates the tedious manual coding required to make your VisualNEO Win applications resize gracefully. With just a few simple actions, you can register any object on your publication and choose how it behaves when the window changes size. Whether you need buttons to scale proportionally with the window (SCALE mode) or maintain their original size while repositioning intelligently (MOVE mode), this plugin handles it automatically with smooth, professional results.
Key Benefits:

Zero Coding Required - No complex math or resize event handlers to write. Simply register your objects through an intuitive dialog and let the plugin do the work.

Two Flexible Modes - SCALE mode resizes objects proportionally for dynamic layouts, while MOVE mode keeps objects at their original size but repositions them perfectly as the window grows or shrinks.

Professional Results - Uses Windows' built-in deferred positioning API for flicker-free, smooth resizing that looks polished and professional.
Simple Setup - Just three actions: capture the original window size, register your objects, and you're done. The plugin automatically handles all window resize events from that point forward.

Perfect for creating modern, responsive VisualNEO Win applications that adapt beautifully to any screen size or user preference!

Hope you find this useful for you resizable publications...
Cheers

Make sure you delete the old Resize Helper plugin before installing this version...

There was a bug in an older version...
Install AutoResizeObjectsV-2 below.

Uploaded files:

You need to login to have access to uploads.

luishp, Vadim and 9 other users have reacted to this post.

#2 · November 25, 2025, 2:05 pm

@anthony-latorre and @emmanuel-fernandez

I absolutely love what you've been doing with PureBasic and VisualNeo Win.. You inspired me to check out PB for myself the other day, as if I don't have enough languages in my head.. ;) Anyways, thanks so much!

I had a question about the PureBasic compiler. I tried to compile a plug-in with it but I could not output a 32bit dll.. searching their site, I believe it requires a purchase to create 32-bit dlls, Correct me if I'm wrong.. Anyways, it was fun..

Brad

luishp, Anthony LaTorre and emo have reacted to this post.

#3 · November 25, 2025, 3:36 pm

Thank you Brad, coming from you that's quite a complement... I've purchased a few of your plugs and downloaded some free ones... and they are all excellent. I have the paid PureBasic version, so I wouldn't know if the compiler works with the free version. I think I remember reading somewhere that the free version will compile small programs... but I'm not quite sure...

The compiler option settings I use are: Exactable Format: Shared Dll, Enable modern theme support, Enable DPI aware executables, Use Compiler: PureBasic 6.21 (Windows -x86). And in the Compile/Run tab: Enable Debugger, and Create temporary executable in the source directory...

Hope that helps...

luishp, Darbdenral and iretz have reacted to this post.

#4 · November 26, 2025, 10:58 am

@anthony-latorre

I appreciate that, thank you.. Yes, I just added Pure Basic to my arsenal, it's actively developed with a nice community and now I managed to produce a quick plugin with Claude too. I use Claude with Delphi when needed but with Pure Basic it did everything for me, lol :)

However, every plugin I compile works fine inside the VisualNeo Win, but when I exit VisualNeo Win I get a runtime error 216. This includes, all your plugins, emo's and mine.. I compiles them here, they work but same error when leaving VNW.. I tried their beta 32bit Version too, no change, wiped clean reinstalled, nothing works. hahah.. crazy

Anthony LaTorre has reacted to this post.

#5 · November 26, 2025, 12:25 pm

Brad, I get the same 216 runtime error... but it is intermittent, keeping my fingers crossed it doesn't show up in someone's compiled exe.

Brad here's something you may find useful... When I was working on the Window Resize Helper, there was an issue when the application lost focus and then regained focused. The plugin would no longer scale and position objects properly... Claude tried to fix it... but didn't come up with a solution. I must have recompiled the plugin in PureBasic about 20 times trying Claude's suggested fixes, even Claude gave up and said it must be a broken Windows API issue... The only workaround I could come up with was putting code in the Deactivate Action tab that restored the publication window to its design-time dimensions, and then reinitializing the plugin. Not the most elegant solution when you click out of a maximized window and the App window scales back to 1024 x 768.

I wasn't buying Claude's broken Windows API explanation, so I uploaded the PureBasic code to a custom Chat GPT program I created for building plugins with PureBasic: https://chatgpt.com/g/g-68a86b36f5f08191931a11056fb29364-visualneo-win-plugin-helper

I told the customGPT the problem I was having and then asked it to identify the potential issues... It did, then I instructed the GPT to create a report and make it available as a PDF file I could download. I then uploaded the report to Claude AI and instructed it to look over the report for potential fixes... It did... and found the offending line of code that was breaking the plugin, applied the fixes, and coded a working plugin that solved the issue...

Moral of the story : Always get another AI's opinion... lol...
Feel free to use my CustomGPT... All you need is a free ChatGPT account.

Cheers

alangonzalez91 and Darbdenral have reacted to this post.

#6 · November 26, 2025, 2:53 pm

Quote from Anthony LaTorre on November 26, 2025, 12:25 pm

Brad, I get the same 216 runtime error... but it is intermittent, keeping my fingers crossed it doesn't show up in someone's compiled exe.

Well that's comforting to know, I thought I was going to be the only one.. The good news is. The only "issue" is a harmless error message when you exit the IDE. That's acceptable for a working plugin!

As Claude says..

Perfect! That's actually GOOD news. The Runtime Error 216 only happens when exiting the VisualNEO Win IDE itself, not:

When running compiled applications
When testing inside the IDE
During normal plugin operation

This means it's a harmless cleanup order issue between PureBasic's DLL unloading and VisualNEO Win's shutdown process. It doesn't affect functionality at all.

Conclusion: Your Plugin is fully functional and working correctly. The Runtime Error 216 is just an annoying IDE exit quirk that:

Doesn't break anything
Doesn't affect end users
Doesn't affect testing
Is probably inherent to how PureBasic 6.21 handles DLL cleanup with Delphi applications

You can safely ignore this error. It's a cosmetic issue, not a functional problem.

Hahah .. Ok, It's still annoying but I'm happy still.. :) Thanks!!!!

luishp, Vadim and 2 other users have reacted to this post.

#7 · January 7, 2026, 8:25 pm

NEW PLUGIN! Auto Resize Objects 1/7/26... This plugin has been totally rewritten. Just 3 actions for automatic resizing and positioning of objects...

Download AutoResizeObjectsV-2 from the 1st post of this topic...

luishp, Vadim and 3 other users have reacted to this post.

#8 · January 8, 2026, 2:09 am

I'm really happy, one of the most useful plugins in visualneo win. Thank you

luiz and Anthony LaTorre have reacted to this post.

#9 · January 8, 2026, 2:16 am

You're welcome... make sure you download AutoResizeObjectsV-2 from the 1st post in this topic... The other version had a bug when trying to resize multiple containers on a page...

Enjoy the plugin...

Vadim, rasl and Sinesi Giuseppe have reacted to this post.

#10 · January 10, 2026, 7:00 pm

Congratulations on the plugin! I have a question: if I use the master page display feature, how should I handle it? Should I put it in a container and call `ResizeWin_RegisterObject "MasterContainer" "SCALE"` on each page? Thanks.

Anthony LaTorre has reacted to this post.

#11 · January 10, 2026, 8:49 pm

I haven't had the opportunity to test objects that are on the master page. Since master page objects are rendered on the page, I would first try to put the resize code in the page startup event that will be displaying the master container... If that doesn't work try it in the container resize event... And don't forget to clear the registered object before another call:

ResizeWin_ClearRegisteredObjects
ResizeWin_RegisterObject "MasterContainer" "SCALE"

Hope that helps, and it would be interesting to know how you made out...

#12 · January 11, 2026, 2:47 am

Thanks, I'll try it and let you know the results.

#13 · January 11, 2026, 11:43 pm

Hi, I tried your suggestion but I couldn't get it to resize to the master page container

#14 · January 12, 2026, 12:21 am

Thanks for trying... Now we know that objects can't be resized from the master page. They must be present on the page to scale or reposition.

Thanks again for testing the plug.

#15 · January 12, 2026, 6:42 pm

Thank you for creating and sharing it.

Anthony LaTorre has reacted to this post.

NEW PLUGIN! Auto Resize Objects 1/7/26 - Forum

NEW PLUGIN! Auto Resize Objects 1/7/26

NEW PLUGIN! Auto Resize Objects 1/7/26... This plugin has been totally rewritten. Just 3 actions for automatic resizing and positioning of objects...

NEW PLUGIN! Auto Resize Objects 1/7/26... This plugin has been totally rewritten. Just 3 actions for automatic resizing and positioning of objects...