|
|
@@ -34,17 +34,17 @@ The following features are either planned (\planned), under construction (\progr
|
|
|
\item[\done] Showing pseudocode and the position where the algorithm currently is.
|
|
|
\begin{itemize}
|
|
|
\item[\done] Clicking on the pseudocode to set a breakpoint at (not \reserved{goto}) a specific location.
|
|
|
- \item[\planned] Customizing the font size of the code.
|
|
|
+ \item[\done] Customizing the font size of the code.
|
|
|
\end{itemize}
|
|
|
\item[\planned] Showing a legend to explain the shapes and colors.
|
|
|
\item[\done] Showing tooltips when hovering over code lines and nodes in the graph that show the state of the variables.
|
|
|
- \item[\planned] Hovering the mose over a node to highlight it in all layouts.
|
|
|
+ \item[\done] Hovering the mose over a node to highlight it in all layouts.
|
|
|
\end{itemize}
|
|
|
\item[\done] Running the algorithm step by step manually.
|
|
|
\item[\done] Running the algorithm step by step with configurable delay (\enquote{automatic execution}).
|
|
|
\item[\done] Running the algorithm only on the expanded parts of the source code (\enquote{step overrun}).
|
|
|
\begin{itemize}
|
|
|
- \item[\planned] Right clicking the code to expand or collapse all lines up to a specified level.
|
|
|
+ \item[\done] Right clicking the code to expand or collapse all lines up to a specified level.
|
|
|
\end{itemize}
|
|
|
\item[\done] Using debugger-like commands such as \enquote{step into}, \enquote{step over}, \enquote{step out}.
|
|
|
\item[\done] Adding buttons and other graphical elements to support the user interface (low priority, see figure~\ref{fig:sketch}).
|
|
|
@@ -64,6 +64,8 @@ The following features are either planned (\planned), under construction (\progr
|
|
|
The most important unsolved issues are listed here.
|
|
|
For a complete list, see \url{https://koljastrohm-games.com:3000/GraphDrawer/NodeShuffler/issues}.
|
|
|
\begin{itemize}
|
|
|
- \item Our implementation does not behave correctly for very few graphs, see section ~\ref{sec:assumptions} and figures~\ref{fig:error_disconnected_img},~\ref{fig:error_connected_img},~\ref{fig:error_disconnected}, and~\ref{fig:error_connected}.
|
|
|
- \item Swing is not thread-safe, but we are using multiple threads, so every now and then there are race conditions causing mostly \code{ArrayIndexOutOfBoundsException}s and \code{NullPointerException}s.
|
|
|
+ \item \sout{Our implementation does not behave correctly for very few graphs, see section ~\ref{sec:assumptions} and figures~\ref{fig:error_disconnected_img},~\ref{fig:error_connected_img},~\ref{fig:error_disconnected}, and~\ref{fig:error_connected}.}
|
|
|
+ We don't know what caused this problem but after a larger rewrite of the algorithm this is fixed, at least for connected graphs.
|
|
|
+ \item \sout{Swing is not thread-safe, but we are using multiple threads, so every now and then there are race conditions causing mostly \code{ArrayIndexOutOfBoundsException}s and \code{NullPointerException}s.}
|
|
|
+ Presumably fixed.
|
|
|
\end{itemize}
|
