Found 8 packages
A simple extension for Window object in XAML and WPF projects. It save and restore position and size of any Window used into your WPF application. The usage is very simple: <Window xmlns:wsh="clr-namespace:WindowStateHelper" wsh:WindowStateHelper.Active="true" /> Declare the namespace for the extension and set Active property to "true" value as shown above. Since this moment, the extension takes care of saving the state when the window is closed, and restoring the state when the window is re-opened. This extension saves the state information in a file contained into the current directory of your application. The name of the file is: <application_name>-<window_name>.txt
A .NET6 WPF metro window featuring glow, configurable colors, menu integrated in title bar, alternative designs, saving and restoring of window position and minimize/maximize/restore/close animations.
WPF ToolKit contains useful services, converters to work with WPF. It targets MVVM pattern.
AutoWindowPlacement provides ability for WPF to preserve Window position and state between sessions.
A simple extension for Window object in XAML and WPF projects. It save and restore position and size of any Window used into your WPF application. The usage is very simple: <Window xmlns:wsh="clr-namespace:WindowStateHelper" wsh:WindowStateHelper.Active="true" /> Declare the namespace for the extension and set Active property to "true" value as shown above. Since this moment, the extension takes care of saving the state when the window is closed, and restoring the state when the window is re-opened. This extension saves the state information in a file contained into the current directory of your application. The name of the file is: <application_name>-<window_name>.txt
A library that provides a function to save information such as window size, position, and maximized state in WinUi3 in a Json file when exiting, and load it at the next startup to restore the previous state.
Key reasons for using the Rubik's Cube MVVM Toolkit in your applications: a. To get rid of the need to get/set Command properties in the view model. b. To simplify work with the configuration file. Common settings, such as Window State and Position of Window, are already implemented. c. To simplify work with validation of objects and view models. d. To detect incorrect command names/settings/validators
StyloFlow Retrieval Documents - Document chunking strategies (sliding window, semantic splits), MMR reranking, and position-based weighting for RAG and retrieval systems.