CoreSuite.PictureViewer 1.0.0

PictureViewer

Image-path viewer with navigation, add, remove and save commands.

Overview

PictureViewer extends UserControl and provides image-path viewer with navigation, add, remove and save commands.

It is designed for .NET 8 Windows Forms applications and can be configured in code or through the Visual Studio designer where designer support applies.

Features

• Maintains an ordered collection of image file paths.
• Provides first, previous, next and last navigation.
• Includes add, remove and save commands.
• Supports custom command images, colors and tooltip captions.
• Uses the standard Windows Forms event and component model.
• Includes English XML documentation for the public API.
• Requires no third-party packages.

Requirements

• Windows Forms
• .NET 8 for Windows (net8.0-windows)

Installation

Install the package from NuGet:

dotnet add package CoreSuite.PictureViewer

Or use the Visual Studio NuGet Package Manager and search for:

CoreSuite.PictureViewer

Namespace

Imports CoreSuite.Controls

Quick start

Imports CoreSuite.Controls

Dim Viewer As New PictureViewer With {
    .MaximumPictures = 10,
    .CounterMask = "{0} of {1}",
    .ShowControlBar = True,
    .ShowCounterBar = True
}
Viewer.AddPictures({"C:\Images\one.png", "C:\Images\two.jpg"})
Viewer.MoveFirst()

Designer usage

After installing or referencing the package, add PictureViewer from the Toolbox or create it in code. Properties configured in the Windows Forms Designer are serialized into InitializeComponent and remain available at runtime.

API reference

PictureViewer

Represents image-path viewer with navigation, add, remove and save commands.

Public Class PictureViewer
    Inherits UserControl

Main members

Behavior and validation

• Property changes take effect immediately unless a method explicitly starts or applies an operation.
• Callers should validate user input and referenced objects before performing application-specific work.
• Events use the standard Windows Forms event model and should be handled on the UI thread.

Standard functionality

Because PictureViewer inherits from UserControl, the standard public members of that base type remain available unless the control intentionally hides or overrides them.

Resource and lifetime considerations

• Dispose components, controls, images, fonts and menus created dynamically when your application owns them.
• Keep referenced controls alive for as long as a component is attached to them.
• File-based operations should receive valid, accessible paths.

Package information

License

This package is distributed under the MIT License defined by the CoreSuite repository.