WARNING: Don't run this snippet if you are unsure of what it does or if you didn't understand clearly what is written down here.
I was playing around with DBPro and found this strange property of the window manipulation functions.
Check this out:
sync on : sync rate 60
a as float : a2 as float
hide window
set window layout 0,0,0
cls rgb(255,255,255)
do
x = desktop width()/2
y = desktop height()/2
d = 200
d2= 200
a = wrapvalue(a+1)
a2= wrapvalue(a2+5)
mx = (sin(a)*d)+x
my = (cos(a)*d)+y
mx2 = (sin(a2)*d2)+mx
my2 = (cos(a2)*d2)+my
tm = ((timer()/30) mod 360)
w = (sin(tm)*100)+150
h = (cos(tm)*100)+150
set window size w,h
//set window position mx2,my2
sync
loop
IMPORTANT: Once you run this code, the White Window of Hell will apear and start blinking on your screen and it is IMPOSSIBLE to close it even with the Task Manager.
To get rid of it, you'll need to log out or restart your machine.
WHY THIS HAPPENS:
When you use the HIDE WINDOW command, the window is hidden (duuh!) but, when you use any window resizing command, it must be un-hidden for a little while to apply the change. Once it was resized, it is hidden again automatically.
When you hide the window, it is also hidden in the Task Manager and when it is resized, it is shown there for half a second and then it goes away. It appears and disappears so fast you can't even select it before it goes away, making it impossible to close it by force.
The same happens to the window controls. ALT+F4 doesn't work because the window is not there for long enough to the command to be applied, then it CAN'T BE CLOSED BY ANY EXISTING WAYS!
Logging out and restarting kill it, Windows seem to have no problem taking care of it by itself - at least in Windows 10, I don't know how it will behave in older versions.
My idea here was to prank you a little, in part because it happened with me when I compiled this stuff and couldn't close it (it was running while I was posting this).
Other thing: think what DBPro can do if used for evil purposes. I didn't heard of viruses or bad commands written in DBPro, but this little piece of code shows that YES, DBPro can do bad things.
For example, if you DISABLE SYSTEM KEYS and use SET MOUSE POSITION to make mouse outside of the screen, you CAN'T CLOSE IT BY LOGGING OFF OR RESTARTING because you CAN'T CLICK ANYWHERE OR USE ALT+TAB TO RETRIEVE CONTROL OF YOUR COMPUTER! The only way, with these commands, would be pushing out the plug and rebooting manually by turning off the power. Not a virus, but think how terrible it could look if happened to a newbie user.
God is real - except if declared as integer.
