It seems resizing feature is not included in the imagebox about cyotek.windows.forms.imagebox

[cyotek]

Do you mean dragging and resizing selection regions? If so, correct, this wasn't added to the core control.

Partly, this is to avoid bloat and piling on feature after feature that the majority of users won't use and partly because I didn't want to complicate the base control for when it needs to be extended to add any custom stuff. After all, one person wants to select something. Another person wants to select something and resize it. And someone else wants to select lots of things and resize lots of things.

I remember well the obscene size and bloat of some of the major 3rd party control vendors out there which is why I'm not trying to make this control fit every conceivable scenario. However, I do think it's probably time I rolled the resize functionality into the main control, it seems to be the most common user request.

[corientdev]

Thanks for the wonderful library you seems to be genius. Your user controls are just perfect i am glad that you are providing it for free. Keep it up lot of blessings.

& Thanks for looking into it and any work around for now by which i can compile this functionality in core control?

[cyotek]

I wouldn't go that far, but thanks for the compliment and I'm glad you enjoy the control.

If you are compiling the source yourself, you probably have two options.

The first, and easiest, option would be to take the ImageBoxEx control from the demo project (and the DragHandle, DragHandleAnchor and DragHandleCollection classes) and add them to the main ImageBox library, then change the visibility of each from internal to public. You'd probably want to change the namespace of each as well to remove the .Demo suffix. Now compile the library and just use ImageBoxEx where you would normally use ImageBox.

(Or you could just create a new library project, add the four classes to that (along with the NuGet package) and then just reference your custom library in your code - that's probably the simplest solution of all)

The second and more complicated option is to add the 3 Drag* classes (and modifications) as described above, and then merge the ImageBoxEx control into the ImageBox control. A lot of this will just be moving new properties, events, and methods so that shouldn't be too much of a problem. However, any override method will need to be manually merged into the original method, so you don't break either the old functionality, or the new functionality.

The third option would be to wait until this source is updated, but in fairness I can't say when that would be - I need make sure the new API is a good fit and isn't going to cause issues down the line that would then involve breaking changes.

Edit: And I should probably try and fix disabling scrollbars bug that a couple of users have reported before I go about adding new features :)

[corientdev]

Thank you so much Richard. I will try and let you know.. :)

Good day!

[corientdev]

I don't know how better its gonna work but i compiled it successfully with all the events and properties of imageboxex