• You've discovered RedGuides 📕 an EverQuest multi-boxing community 🛡️🧙🗡️. We want you to play several EQ characters at once, come join us and say hello! 👋
  • IS THIS SITE UGLY? Change the look. To dismiss this notice, click the X --->
Resource icon

Work in Progress RGManager (beta) v1.6.0.9

Download
Bug Fixes:
-Fixed an issue where the logic used to create new SEQ offsets was failing to appropriately translate myseqserver.ini in to the pre-determined JSON structure.
Changes:
-MacroQuest button logic is now determined every time the MQ path is changed as opposed to just when the MQ path is changed to a valid MQ2Main.dll directory
Changes:
-Modified the view model structure so that MacroQuest existing resource paths are now appropriately updated when a valid path is passed through the Local Paths MacroQuest textbox.

Bug Fixes:
-Fixed a issue where the existing MacroQuest path input and new MacroQuest path input could potentially desync when using the file dialog, causing some logic to operate over the old path and some to operate over the new.
Bug Fixes:
-Fixed a bug where a potential null value could be thrown when attempting to get the parent grid of a resource that was attempting to fix it's state-based control.
Bug Fixes:
-Fixed a bug where, when a resource throws no file associated after being downloaded from the All Resources page, an issue could occur if the resource was watched and then clicked on in the Watched Resources page.
Changes:
-Modified path assignment for the MQ Path to allow for detection of MQ2Main.dll in the assigned root's file tree after losing focus to more accurately determine the appropriate MQ Page controls and give user-end feedback.
Bug Fixes:
-Fixed a bug where excluding/including a part of a resource in the Resource File Excludes would fail due to an error with the updated view model structure that came with 1.6.0.0
Bug Fixes:
-Fixed a bug where certain resource lists could potentially throw over null values where it shouldn't be possible.
Bug Fixes:
-Fixed a bug where, when the ResourceHandler returned a "No Files" error, filtered resources could potentially still be included in existing resource lists after removal causing a null reference when attempting to access the information of a resource that was already removed from the parent resources list.
New Stuff:
-New modifier for debug console command resourcehandlermods: -alwaysadmin/-askforelevation which can be used to dictate whether or not the resource handler always launches with elevation
-Watching/Stop Watching icons have been modified (by theme) to be much more apparent as to the watching status of the resource.
-You can now enable auto saving via the Application settings page! This allows the user to enable auto saving all settings on a user-determinant interval to prevent any unintended data loss. This is enabled by default (on new installations) with a 15 minute interval.

Changes:
-First half of MVVM instantiation has been completed, UI thread manipulation should be relatively more optimized.
-Structures for downloading have been refactored in their entirety.
-Pipeline communication for downloading has been modified to be cleaner and more optimized given the new downloads structure. This should help to alleviate some of the optimization issues downloading can cause.
-Pipeline's should now appropriately terminate themselves upon terminating the application environment as opposed to waiting until the resource handler has terminated.

Bug Fixes:
-Fixed a bug where, when downloading a externally hosted resource, the resource handler could potentially return an incorrect value resulting in improper handling of a fileless resource.
-Fixed a bug where settings could fail to save due to a potential null value on the user-end.
-Fixed a bug where some objects could potentially block others while resizing/maximizing in certain settings panels.
-Fixed a bug where certain framework objects could have a small graphical bug shortly before disposal due to a fired PropertyChanged event.
-Fixed a bug where multiple instances of an interval for dispatcher timers would be populated upon main window initialization

NOTE: There's a great deal of changes to the view model structure of the application as well as the download structure. I've tested extensively but there could very well be some issues lingering here or there due to the changes from the older logic. If you run in to anything, please don't hesitate to reach out and let me know!
Back
Top