From 7ae6f158dead16cbd99ec12b94d4149bf7e6f1a2 Mon Sep 17 00:00:00 2001
From: omar <ocornut@users.noreply.github.com>
Date: Thu, 28 Dec 2017 18:20:20 +0100
Subject: [PATCH] Updated Developer Tips (markdown)

---
 Developer-Tips.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/Developer-Tips.md b/Developer-Tips.md
index 662fae6..48aa847 100644
--- a/Developer-Tips.md
+++ b/Developer-Tips.md
@@ -1,5 +1,7 @@
 ### Using breakpoints
 Using debugger breakpoints can be tedious in an interactive application dealing with lots of data. Even more so as the state of the application may be so reliant on mouse and keyboard inputs. One convenient trick is filter breakpoint based on custom conditions, e.g checking for the Alt key modifier to be pressed:
-`if (ImGui::GetIO().KeyAlt)
-    printf(""); // Set a debugger breakpoint here!`
+
+`if (ImGui::GetIO().KeyAlt)`
+`    printf(""); // Set a debugger breakpoint here!`
+
 So you can setup your UI state for debugging (open windows, mouse position, active action etc.) and then only when you press ALT your breakpoint will trigger.