Merge pull request #13 from MuertoGB/dev

112 merge to main

CHANGELOG.md

@@ -1,5 +1,6 @@
 <h4 align="center">Version History</h4>
 <p align="center">
+  <a href="#version-112">V1.1.2</a> •
   <a href="#version-111">V1.1.1</a> •
   <a href="#version-110">V1.1.0</a> •
   <a href="#version-103">V1.0.3</a> •
@@ -17,6 +18,16 @@
   <a href="#version-034">V0.3.4</a>
 </p>
 
+## Version 1.1.2
+
+#### Enhancements:
+- User Interface improvements.
+- Altered the functionality of export dialogues. Rather than displaying the export path, users will now be prompted to decide whether they want to navigate to the file directly in an explorer window.
+
+#### Bugs:
+- Fixed image and text display issues when the Operating System UI scaling is set to 100% size.
+- Fixed the custom initial directory setting not being reflected immediately when a firmware is not loaded, and a user changes the path.
+
 ## Version 1.1.1
 
 #### New:

MANUAL.md

@@ -49,21 +49,21 @@ Opens the overflow menu with various extra options:
   <img src="files/manual/overflowmenu.png">
 </kbd>
 
-**'Local Directory':**\
-Opens the working directory where the executable is located.
-
-**'Backups Directory':**\
+**'Backups Folder':**\
 Navigates to the Backups directory. This is the default location where zipped file backups are exported.
 
-**'Builds Directory':**\
+**'Builds Folder':**\
 Navigates to the Builds directory within the working directory, this is where edited binaries are automatically saved.
 
-**'Fsys Store Directory':**\
+**'Fsys Store Folder':**\
 Navigates to the Fsys Store directory within the working directory. This is the default location where Fsys Stores are exported.
 
-**'ME Region Directory':**\
+**'ME Region Folder':**\
 Navigates to the ME Region directory within the working directory. This is the default path where ME regions are exported.
 
+**'Working Directory':**\
+Opens the current working directory where the executable is located.
+
 **'Changelog':**\
 Opens a browser window directly to the application's changelog.
 
@@ -300,37 +300,29 @@ This section explains the firmware editor window and its functionality.
 #### Fsys Store:
 
 <kbd>
-  <img src="files/manual/fsys_replace.png">
+  <img src="files/manual/patcher_fsys.png">
 </kbd>
 
-When the checkbox is activated, an open file dialog will be prompted, enabling the selection and opening of the new Fsys Store. If you want to choose a different file, simply click the 'Change File' button to reopen the file dialog.
-
-The application will verify the new Fsys Store, if CRC masking is require this will be done automatically at build time.
-
-> 🛈 The `Replace Serial Number` option is not available when `Replace Fsys Store` is selected.
+This section comprises of two main functions.
 
----
+When the "Replace Fsys Store" switch is activated, an open file dialog will be prompted, enabling the selection and opening of the new Fsys Store. If you want to choose a different file, simply click the '...' button to reopen the file dialog.
 
-#### Serial Number:
+The application will verify the new Fsys Store, if CRC masking is require this will be done automatically at build time.
 
-<kbd>
-  <img src="files/manual/serial_replace.png">
-</kbd>
+> 🛈 Only one option is available at a time. If you choose one, the other is disabled.
 
-When the checkbox is activated, it will enable the 'SSN' textbox, allowing input of a new serial number. Once a valid serial number is entered, the Hardware Configuration code (HWC) will be automatically determined based on the provided serial number. It is important to note that you cannot change the HWC separately from the serial number. The HWC must match the serial number and cannot be modified independently.
+When the "Replace Serial Number" switch is activated, it will enable the 'SSN' textbox, allowing input of a new serial number. Once a valid serial number is entered, the Hardware Configuration code (HWC) will be automatically determined based on the provided serial number. It is important to note that you cannot change the HWC separately from the serial number. The HWC must match the serial number and the application does not allow independent modification.
 
 The application will automatically enforce the required length of the serial number, allowing for either 11 or 12 characters. It will also provide validation to ensure that only valid characters are entered. This helps to ensure that the serial number input meets the necessary criteria and maintains the expected format.
 
 The editor will automatically verify and mask the Fsys Store CRC32 after the serial number patching is complete.
 
-> 🛈 The `Replace Fsys Store` option is not available when `Replace Serial Number` is selected.
-
 ---
 
 #### NVRAM:
 
 <kbd>
-  <img src="files/manual/nvram_clear.png">
+  <img src="files/manual/patcher_nvram.png">
 </kbd>
 
 In this section, you have the option to clear specific NVRAM stores. By selecting 'Clear VSS Store', a general PRAM reset will be performed, similar to using CMD + SHIFT + P + R on the Mac keyboard. This action helps in resetting parameters stored in the VSS Store.
@@ -341,13 +333,13 @@ The NSS store's specific purpose is currently unknown to me. It is included as a
 
 ---
 
-#### ME Region:
+#### Intel ME:
 
 <kbd>
-  <img src="files/manual/me_replace.png">
+  <img src="files/manual/patcher_intelme.png">
 </kbd>
 
-When the checkbox is activated, an open file dialog will be prompted, allowing selection of a donor or clean Management Engine (ME) firmware. This feature proves useful for scenarios such as migrating a ME Region from a faulty UEFI to a donor UEFI. Additionally, it can be utilized to write a configured ME Region from a matching clean Apple firmware.
+When the switch is activated, an open file dialog will be prompted, allowing selection of a donor or clean Management Engine (ME) firmware. This feature proves useful for scenarios such as migrating a ME Region from a faulty UEFI to a donor UEFI. Additionally, it can be utilized to write a configured ME Region from a matching clean Apple firmware.
 
 A repository of clean Apple firmware can be found here on [Github](https://github.com/gdbinit/firmware_vault). This repository provides a collection of clean Apple firmware files containing clean and configured ME regions.
 
@@ -360,7 +352,7 @@ For users who require a higher level of certainty and guidance in replacing the
 #### Output:
 
 <kbd>
-  <img src="files/manual/output.png">
+  <img src="files/manual/patcher_output.png">
 </kbd>
 
 This section includes a single button and the output log. By clicking the 'Save Log' button, a save file dialog will be prompted, allowing you to export the log text to a file of your choice.

README.md

@@ -1,7 +1,7 @@
 <h1 align="center">
 <img width="200" src="files/images/img128px.png" alt="SMCFT Logo">
 <br>
-Mac EFI Toolkit V1.1.1
+Mac EFI Toolkit V1.1.2
 </h1>
 
 <h4 align="center">A tool for analysis of Mac BIOS/UEFI, with limited editing capabilities.</h4>
@@ -83,7 +83,8 @@ This application provides support for most Mac BIOS/UEFI, with the exception of
 
 | Version| Release Date| Latest | Channel |
 |--------|-------------|--------|---------|
-|[1.1.1](https://github.com/MuertoGB/MacEfiToolkit/releases/latest)| 2nd September, 2023 | Yes | Stable |
+|[1.1.2](https://github.com/MuertoGB/MacEfiToolkit/releases/latest)| 25th September, 2023 | Yes | Stable |
+|[1.1.1](https://github.com/MuertoGB/MacEfiToolkit/releases/111)| 2nd September, 2023 | No | Stable |
 
 > 📋 View the full changelog [here](CHANGELOG.md)
 

files/app/version.xml

@@ -1,11 +1,11 @@
 <?xml version="1.0" encoding="utf-8"?>
 <data>
  <MET>
-    <VersionString>1.1.1</VersionString>
-    <Build>230902.0121</Build>
-    <ReleaseDate>02.09.2023</ReleaseDate>
+    <VersionString>1.1.2</VersionString>
+    <Build>230925.2100</Build>
+    <ReleaseDate>25.09.2023</ReleaseDate>
     <Channel>Stable</Channel>
-    <SHA256>c4b77627d620a411e31afae1bf76a9265af88c4ac6a3a45645a1d08161fc6b38</SHA256>
-    <VT>https://www.virustotal.com/gui/file-analysis/MmFmNzA4YzE1MDFlMmMwY2NkMTU1MTZkNzFlZmVhMzk6MTY5MzYxNTY0MQ==</VT>>
+    <SHA256>3d0372b74fd1301a90cf44f12d975839471c13b779e4658d4b6c07ae230e46f3</SHA256>
+    <VT>https://www.virustotal.com/gui/file/3d0372b74fd1301a90cf44f12d975839471c13b779e4658d4b6c07ae230e46f3</VT>>
  </MET>
 </data>

mefit/Program.cs

@@ -34,7 +34,7 @@ internal struct METPath
 
     internal struct METVersion
     {
-        internal static readonly string Build = "230902.0121";
+        internal static readonly string Build = "230925.2100";
         internal static readonly string Channel = "Stable";
     }
 
@@ -240,12 +240,12 @@ internal static void PerformMetAction(Form owner, MetAction action)
 
             if (action == MetAction.Restart)
             {
-                title = "Restart application";
+                title = "Restart";
                 message = "Are you sure you want to restart the application?";
             }
             else if (action == MetAction.Exit)
             {
-                title = "Exit application";
+                title = "Quit";
                 message = "Are you sure you want to quit the application?";
             }
             else

mefit/Properties/AssemblyInfo.cs

@@ -33,6 +33,6 @@
 // You can specify all the values or you can default the Build and Revision Numbers
 // by using the '*' as shown below:
 // [assembly: AssemblyVersion("1.0.*")]
-[assembly: AssemblyVersion("1.1.1")]
-[assembly: AssemblyFileVersion("1.1.1")]
+[assembly: AssemblyVersion("1.1.2")]
+[assembly: AssemblyFileVersion("1.1.2")]
 [assembly: NeutralResourcesLanguage("en")]