|
| 1 | +name: "Ask a question, report a bug, request a feature, etc." |
| 2 | +description: "Ask any question, discuss best practices, report a bug, request a feature." |
| 3 | +body: |
| 4 | + - type: markdown |
| 5 | + attributes: |
| 6 | + value: | |
| 7 | + FOR FIRST-TIME USERS ISSUES COMPILING/LINKING/RUNNING or LOADING FONTS, please use [GitHub Discussions](https://github.com/ocornut/imgui/discussions) |
| 8 | + For anything else: we are happy to use 'GitHub Issues' for many types of open-ended questions. We are encouraging 'Issues' becoming a large, centralized and cross-referenced database of Dear ImGui contents. |
| 9 | +
|
| 10 | + Be mindful that messages are being sent to the e-mail box of "Watching" users. Try to proof-read your messages before sending them. Edits are not seen by those users. |
| 11 | + - type: markdown |
| 12 | + attributes: |
| 13 | + value: | |
| 14 | + **Prerequisites:** |
| 15 | + - I have read [Frequently Asked Questions](https://github.com/ocornut/imgui/blob/master/docs/FAQ.md). |
| 16 | + - I have read [Contributing Guidelines -> General Advices](https://github.com/ocornut/imgui/blob/master/docs/CONTRIBUTING.md#getting-started--general-advice). |
| 17 | + - I have read [Contributing Guidelines -> How to open an Issue](https://github.com/ocornut/imgui/blob/master/docs/CONTRIBUTING.md#how-to-open-an-issue). |
| 18 | + - I have searched [Github Issues and PR](https://github.com/ocornut/imgui/issues?q=) for discussion of similar topics. |
| 19 | +
|
| 20 | + ---- |
| 21 | + - type: input |
| 22 | + id: specs_version |
| 23 | + attributes: |
| 24 | + label: "Version/Branch of Dear ImGui:" |
| 25 | + description: "(please specify if you have made substantial modifications to your copy)" |
| 26 | + value: "Version 1.XX, Branch: XXX (master/docking/etc.)" |
| 27 | + placeholder: "Version 1.XX, Branch: XXX (master/docking/etc.)" |
| 28 | + validations: |
| 29 | + required: true |
| 30 | + - type: input |
| 31 | + id: specs_backend |
| 32 | + attributes: |
| 33 | + label: "Back-ends:" |
| 34 | + description: (or specify when using custom engine/back-ends) |
| 35 | + value: "imgui_impl_XXX.cpp + imgui_impl_XXX.cpp" |
| 36 | + placeholder: "imgui_impl_XXX.cpp + imgui_impl_XXX.cpp or n/a" |
| 37 | + validations: |
| 38 | + required: true |
| 39 | + - type: input |
| 40 | + id: specs_compiler_os |
| 41 | + attributes: |
| 42 | + label: "Compiler, OS:" |
| 43 | + placeholder: "e.g. Windows 11 + MSVC 2022, macOS + Clang 12, Linux + GCC etc." |
| 44 | + validations: |
| 45 | + required: true |
| 46 | + - type: textarea |
| 47 | + id: specs_full |
| 48 | + attributes: |
| 49 | + label: "Full config/build information:" |
| 50 | + placeholder: | |
| 51 | + (If you can run, you may go to 'Demo->Tools->About Dear ImGui->Config/Build Info' to obtain detailed information that you can paste here) |
| 52 | + validations: |
| 53 | + required: false |
| 54 | + - type: textarea |
| 55 | + id: issue_description |
| 56 | + attributes: |
| 57 | + label: "Details:" |
| 58 | + description: "Try to be explicit with your goals, your expectations and what you have tried. Be mindful of [The XY Problem](https://xyproblem.info). What you have in mind or in your code is not obvious to other people. People frequently discuss problems and suggest incorrect solutions without first clarifying their goals. When requesting a new feature, please describe the usage context (how you intend to use it, why you need it, etc.). If you tried something and it failed, show us what you tried. If you are reporting a bug, explain what's the bug, how does it occur, etc. If you are reporting a crash, please include a debugger callstack." |
| 59 | + value: | |
| 60 | + **My Issue/Question:** |
| 61 | +
|
| 62 | + XXX _(please provide as much context as possible)_ |
| 63 | + validations: |
| 64 | + required: true |
| 65 | + - type: textarea |
| 66 | + id: screenshots |
| 67 | + attributes: |
| 68 | + label: "Screenshots/Video:" |
| 69 | + description: "Attach screenshots or gif/videos to clarify the context. They often convey useful information that is omitted by the description." |
| 70 | + placeholder: "(You can drag files here)" |
| 71 | + validations: |
| 72 | + required: false |
| 73 | + - type: textarea |
| 74 | + id: repro_code |
| 75 | + attributes: |
| 76 | + label: "Minimal, Complete and Verifiable Example code:" |
| 77 | + description: "Provide an [MCVE](https://stackoverflow.com/help/mcve) to demonstrate your problem. An ideal submission includes a small piece of code that anyone can paste into one of the examples applications (examples/*/main.cpp) or the demo (imgui_demo.cpp) to understand and reproduce it. Narrowing your problem to its shortest and purest form is the easiest way to understand it, explain it and fix it. Please test your shortened code to ensure it exhibits the problem. Often while creating the MCVE you will solve the problem! Many questions that are missing a standalone verifiable example are missing the actual cause of their issue in the description, which ends up wasting everyone's time." |
| 78 | + value: | |
| 79 | + ```cpp |
| 80 | + // Here's some code anyone can copy and paste to reproduce your issue |
| 81 | + ImGui::Begin("Example Bug"); |
| 82 | + MoreCodeToExplainMyIssue(); |
| 83 | + ImGui::End(); |
| 84 | + ``` |
| 85 | + validations: |
| 86 | + required: false |
| 87 | + - type: markdown |
| 88 | + attributes: |
| 89 | + value: | |
| 90 | + Thank you for taking the time to read prerequisites, filling this template and double-checking your message and your code! |
0 commit comments