Differentiate "undo/skip split" from "previous/next image"

Skip/udo will now actually call command
This makes grouping option obsolete as user now has finer control anyway
UI is a bit cramped, but that should be resolved with UI revamp
Updated README

Author: Avasam

README.md

@@ -33,9 +33,9 @@ This program can be used to automatically start, split, and reset your preferred
 
 - Microsoft Visual C++ 14.0 or greater may be required to build the executable. Get it with [Microsoft C++ Build Tools](https://visualstudio.microsoft.com/visual-cpp-build-tools/)
 - Node is optional, but required for complete linting (using Pyright).
-- Read [requirements.txt](/scripts/requirements.txt) for information on how to install, run and build the python code
+- Read [requirements.txt](/scripts/requirements.txt) for more information on how to install, run and build the python code
   - Run `.\scripts\install.bat` to install all dependencies
-  - Run the app directly with `py .\src\AutoSplit.py [--auto-controlled]`
+  - Run the app directly with `.\scripts\start.bat [--auto-controlled]`
   - Run `.\scripts\build.bat` to build an executable
 - Recompile resources after modifications by running `.\scripts\compile_resources.bat`
 
@@ -59,9 +59,9 @@ This program can be used to automatically start, split, and reset your preferred
 - Once you are happy with your capture region, you may unselect Live Capture Region to decrease CPU usage if you wish.
 - You can save a screenshot of the capture region to your split image folder using the Take Screenshot button.
 
-## Max FPS
+## Avg. FPS
 
-- Calculates the maximum comparison rate of the capture region to split images. This value will likely be much higher than needed, so it is highly recommended to limit your FPS depending on the frame rate of the game you are capturing.
+- Calculates the average comparison rate of the capture region to split images. This value will likely be much higher than needed (unless you [Force Full-Content-Rendering](#Full-Content-Rendering)), so it is highly recommended to limit your FPS depending on the frame rate of the game you are capturing.
 
 ## OPTIONS
 
@@ -72,6 +72,10 @@ This program can be used to automatically start, split, and reset your preferred
   - Histograms: An explanation on Histograms comparison can be found [here](https://mpatacchiola.github.io/blog/2016/11/12/the-simplest-classifier-histogram-intersection.html). This is a great method to use if you are using several masked images.
   - pHash: An explanation on pHash comparison can be found [here](http://www.hackerfactor.com/blog/index.php?/archives/432-Looks-Like-It.html). It is highly recommended to NOT use pHash if you use masked images. It is very inaccurate.
 
+### Full Content Rendering
+
+- Certain windows (namely hardware accelerated ones) won't always render their content. To work around this, you can "Force Full Content Rendering". This option is not reocmmended unless you really need it. It will cause a 10-15x performance drop based on the size of the complete window that's being captured (not the selected region, but rather the actual window size). It can also mess with some applications' rendering pipeline.
+
 ### Show Live Similarity
 
 - Displays the live similarity between the capture region and the current split image. This number is between 0 and 1, with 1 being a perfect match.
@@ -142,11 +146,9 @@ The start image is similar to the reset image. You can only have one start image
 - All of these actions can also be handled by their corresponding buttons.
 - Note that pressing your Pause Hotkey does not serve any function in AutoSplit itself and is strictly used for the Pause flag.
 
-### Group dummy splits when undoing / skipping
-
-If this option is disabled, AutoSplit will not account for dummy splits when undoing/skipping. Meaning it will cycle through the images normally even if they have the dummy flag `{d}` applied to them.
+### Dummy splits when undoing / skipping
 
-If it is enabled, AutoSplit will group dummy splits together with a real split when undoing/skipping. This basically allows you to tie one or more dummy splits to a real split to keep it as in sync as possible with the real splits in LiveSplit/wsplit.
+AutoSplit will group dummy splits together with a real split when undoing/skipping. This basically allows you to tie one or more dummy splits to a real split to keep it as in sync as possible with the real splits in LiveSplit/wsplit. If they are out of sync, you can always use "Previous Image" and "Next Image".
 
 Examples:
 Given these splits: 1 dummy, 2 normal, 3 dummy, 4 dummy, 5 normal, 6 normal.
@@ -192,13 +194,11 @@ The AutoSplit LiveSplit Component will directly connect AutoSplit with LiveSplit
 - Click the Browse buttons to locate your AutoSplit Path (path to AutoSplit.exe) and Settings Path (path to your AutoSplit `.pkl` settings file) respectively.
   - If you have not yet set saved a settings file, you can do so using AutoSplit, and then go back and set your Settings Path.
 - Once set, click OK, and then OK again to close the Layout Editor. Right click LiveSplit -> Save Layout to save your layout. AutoSplit and its settings will now open automatically when opening that LiveSplit Layout `.lsl` file.
-- If you are using any dummy splits, it is recommended that you check the "Group dummy splits when undoing / skipping" checkbox when using LiveSplit integration so that your LiveSplit splits stay in sync with AutoSplit.
 
 ## Known Limitations
 
 - For many games, it will be difficult to find a split image for the last split of the run.
 - The window of the capture region cannot be minimized.
-- Capturing a hardware accelerated window or using Windows 11 altogether will cause performance drops. But as long as the window you are capturing (not the selected region, but rather the actual window size) is not too large, you should still be able to obtain a Max FPS of over 60.
 
 ## Resources
 

res/design.ui

@@ -213,10 +213,10 @@
     </property>
     <property name="geometry">
      <rect>
-      <x>494</x>
-      <y>250</y>
+      <x>340</x>
+      <y>440</y>
       <width>64</width>
-      <height>24</height>
+      <height>21</height>
      </rect>
     </property>
     <property name="focusPolicy">
@@ -232,10 +232,10 @@
     </property>
     <property name="geometry">
      <rect>
-      <x>560</x>
-      <y>250</y>
+      <x>410</x>
+      <y>440</y>
       <width>61</width>
-      <height>24</height>
+      <height>21</height>
      </rect>
     </property>
     <property name="focusPolicy">
@@ -786,7 +786,7 @@
       <x>260</x>
       <y>250</y>
       <width>101</width>
-      <height>24</height>
+      <height>23</height>
      </rect>
     </property>
     <property name="focusPolicy">
@@ -866,9 +866,9 @@
     <property name="geometry">
      <rect>
       <x>125</x>
-      <y>296</y>
+      <y>295</y>
       <width>91</width>
-      <height>22</height>
+      <height>23</height>
      </rect>
     </property>
     <item>
@@ -935,22 +935,6 @@
      <string>Align Region</string>
     </property>
    </widget>
-   <widget class="QCheckBox" name="group_dummy_splits_checkbox">
-    <property name="geometry">
-     <rect>
-      <x>230</x>
-      <y>442</y>
-      <width>261</width>
-      <height>20</height>
-     </rect>
-    </property>
-    <property name="text">
-     <string>Group dummy splits when undoing/skipping</string>
-    </property>
-    <property name="checked">
-     <bool>false</bool>
-    </property>
-   </widget>
    <widget class="QPushButton" name="select_window_button">
     <property name="geometry">
      <rect>
@@ -993,7 +977,7 @@
      <string>Pause</string>
     </property>
    </widget>
-   <widget class="QLineEdit" name="pause_hotkey_input">
+   <widget class="QLineEdit" name="pause_input">
     <property name="geometry">
      <rect>
       <x>300</x>
@@ -1153,6 +1137,44 @@
      <string>Force Full Content Rendering (slower)</string>
     </property>
    </widget>
+   <widget class="QPushButton" name="next_image_button">
+    <property name="enabled">
+     <bool>false</bool>
+    </property>
+    <property name="geometry">
+     <rect>
+      <x>560</x>
+      <y>250</y>
+      <width>61</width>
+      <height>23</height>
+     </rect>
+    </property>
+    <property name="focusPolicy">
+     <enum>Qt::NoFocus</enum>
+    </property>
+    <property name="text">
+     <string>Next Img.</string>
+    </property>
+   </widget>
+   <widget class="QPushButton" name="previous_image_button">
+    <property name="enabled">
+     <bool>false</bool>
+    </property>
+    <property name="geometry">
+     <rect>
+      <x>494</x>
+      <y>250</y>
+      <width>64</width>
+      <height>23</height>
+     </rect>
+    </property>
+    <property name="focusPolicy">
+     <enum>Qt::NoFocus</enum>
+    </property>
+    <property name="text">
+     <string>Prev. Img.</string>
+    </property>
+   </widget>
    <zorder>split_image_folder_label</zorder>
    <zorder>split_image_folder_input</zorder>
    <zorder>browse_button</zorder>
@@ -1207,11 +1229,10 @@
    <zorder>pause_spinbox</zorder>
    <zorder>comparison_method_label</zorder>
    <zorder>align_region_button</zorder>
-   <zorder>group_dummy_splits_checkbox</zorder>
    <zorder>select_window_button</zorder>
    <zorder>image_loop_label</zorder>
    <zorder>pause_hotkey_label</zorder>
-   <zorder>pause_hotkey_input</zorder>
+   <zorder>pause_input</zorder>
    <zorder>set_pause_hotkey_button</zorder>
    <zorder>loop_checkbox</zorder>
    <zorder>auto_start_on_reset_checkbox</zorder>
@@ -1221,6 +1242,8 @@
    <zorder>current_similarity_threshold_number_label</zorder>
    <zorder>capture_region_window_label</zorder>
    <zorder>force_print_window_checkbox</zorder>
+   <zorder>next_image_button</zorder>
+   <zorder>previous_image_button</zorder>
   </widget>
   <widget class="QMenuBar" name="menu_bar">
    <property name="geometry">
@@ -1313,7 +1336,6 @@
   <tabstop>reset_input</tabstop>
   <tabstop>skip_split_input</tabstop>
   <tabstop>undo_split_input</tabstop>
-  <tabstop>group_dummy_splits_checkbox</tabstop>
  </tabstops>
  <resources>
   <include location="resources.qrc"/>