# Bug Report - AlertWindow - VST Plugin - 64 bits - MSVC2013

**URL:** <https://forum.juce.com/t/bug-report-alertwindow-vst-plugin-64-bits-msvc2013/11340>\
**Category:** General JUCE discussion\
**Created:** [August 23, 2013, 4:59pm UTC](https://forum.juce.com/t/bug-report-alertwindow-vst-plugin-64-bits-msvc2013/11340 "2013-08-23T16:59:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![williamk](https://avatars.discourse-cdn.com/v4/letter/w/90ced4/32.png) [@williamk](https://forum.juce.com/u/williamk)\
**Post date:** [August 23, 2013, 4:59pm UTC](https://forum.juce.com/t/bug-report-alertwindow-vst-plugin-64-bits-msvc2013/11340/1 "2013-08-23T16:59:50Z")

</div>

Jules, here´s a bug report. This doesn´t happen for the Juce Demo 64 bits, only with the Juce Audio Plugin VST Demo 64 bits and MSVC2013. (I don´t have any other compiler to test, sorry)

This also happens with the ToolTipWindow, so its something related to fonts or font-sizes? For the test below all I did was compile the Juce Audio Plugin VST Demo, did nothing but added an AlertWindow to test.

Thanks!

&nbsp;

![](http://wusik.com/temp/AlertWindowProblems.jpg)

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [August 23, 2013, 5:10pm UTC](https://forum.juce.com/t/bug-report-alertwindow-vst-plugin-64-bits-msvc2013/11340/2 "2013-08-23T17:10:44Z")

</div>

Try disabling&nbsp;JUCE\_USE\_DIRECTWRITE - the host may be preventing that from working?

But more importantly, **don't use modal windows (or any kind of desktop window!) in a plugin**!

---

<div class="post-metadata">

**Author:** ![yfede](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/yfede/32/506_2.png) [@yfede](https://forum.juce.com/u/yfede)\
**Post date:** [August 24, 2013, 7:35pm UTC](https://forum.juce.com/t/bug-report-alertwindow-vst-plugin-64-bits-msvc2013/11340/3 "2013-08-24T19:35:37Z")

</div>

Well, in some cases you just can't avoid that, don't you think? For example, if you are overriding a preset or losing some saved changes when loading one, a modal dialog is what is required to ask the user for confirmation

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [August 24, 2013, 10:03pm UTC](https://forum.juce.com/t/bug-report-alertwindow-vst-plugin-64-bits-msvc2013/11340/4 "2013-08-24T22:03:28Z")

</div>

If you really, really can't find a better way to handle it, then you _must_&nbsp;at least avoid running a modal loop, and instead show your component modally, and get the result asynchronously via a callback.&nbsp;Setting&nbsp;JUCE\_MODAL\_LOOPS\_PERMITTED=0 will help prevent you messing up.

---

<div class="post-metadata">

**Author:** ![yfede](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/yfede/32/506_2.png) [@yfede](https://forum.juce.com/u/yfede)\
**Post date:** [August 25, 2013, 8:43am UTC](https://forum.juce.com/t/bug-report-alertwindow-vst-plugin-64-bits-msvc2013/11340/5 "2013-08-25T08:43:21Z")

</div>

I'm not sure why this is going to be a problem.. Is it because it could blow up in case one closes the Host application while the modal window is being displayed?

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [August 25, 2013, 9:04am UTC](https://forum.juce.com/t/bug-report-alertwindow-vst-plugin-64-bits-msvc2013/11340/6 "2013-08-25T09:04:24Z")

</div>

Yes - if the plugin gets closed while it's busy&nbsp;running a modal loop, then the stack can't be unwound, and the whole thing dies in a twisted mess.