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

---
 Developer-Tips.md | 5 +++++
 1 file changed, 5 insertions(+)
 create mode 100644 Developer-Tips.md

diff --git a/Developer-Tips.md b/Developer-Tips.md
new file mode 100644
index 0000000..662fae6
--- /dev/null
+++ b/Developer-Tips.md
@@ -0,0 +1,5 @@
+### 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!`
+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.