Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

DarkBASIC Discussion / Annoying 'window resize' bug - anyone found a fix?

Author
Message
Richard Davey
Retired Moderator
21
Years of Service
User Offline
Joined: 30th Apr 2002
Location: On the Jupiter Probe
Posted: 23rd Jan 2007 12:15
Hi all,

I've been having some real fun coding in DB since building some demo progs for the new release. But one thing that constantly annoys me is the way that when you run a DB program to test it, on return to Windows again, all of your windows get really screwed up into a 640x480 size ball. So if I have Photoshop open making graphics for a DB program, then run it, when it comes back Photoshop and all of its dialogs have been resized into 640x480 - which is SO annoying it's untrue!

Does anyone know a work-around for this?

Cheers,

Rich

Heavy on the Magick
Lucifer
18
Years of Service
User Offline
Joined: 26th Dec 2005
Location:
Posted: 23rd Jan 2007 14:07 Edited at: 23rd Jan 2007 14:07
well what i do is minimize all applications before testing stuff in dbc, and it does not bother me because when i have finished doing something in for example flstudio i just minimize it and when i need to do something more i maximize it again and minimize it when not using.


i like pancakes..
Richard Davey
Retired Moderator
21
Years of Service
User Offline
Joined: 30th Apr 2002
Location: On the Jupiter Probe
Posted: 23rd Jan 2007 14:23
Nah, it doesn't work. I've tried that many times and it makes no difference. When I do DB coding I just have to close everything else down first.

Heavy on the Magick
Lucifer
18
Years of Service
User Offline
Joined: 26th Dec 2005
Location:
Posted: 23rd Jan 2007 14:37
Quote: "Nah, it doesn't work."


really? it does seem to work when i do it


i like pancakes..
TDK
Retired Moderator
21
Years of Service
User Offline
Joined: 19th Nov 2002
Location: UK
Posted: 23rd Jan 2007 14:44
I don't get that problem at all - whether I minimize windows before or not!

Out of curiosity, what editor (IDE) are you using?

TDK_Man

Richard Davey
Retired Moderator
21
Years of Service
User Offline
Joined: 30th Apr 2002
Location: On the Jupiter Probe
Posted: 23rd Jan 2007 14:50
I use the default DB IDE because it got so annoying, that way I can just close everything, go into the IDE, work, run, work, run and it doesn't touch my desktop.

If I use Dark Edit (or any other Windows based editor) this problem happens.

I'm on a wide-screen display (1680x1050). Running DB apps also screw with dual-monitor set-ups here. I got Mike to run some test EXEs on his PC and they killed his 2nd monitor when it quit back to Windows and it needed setting up again.

I'm telling you, there's definitely *something* wrong with it somewhere.

Heavy on the Magick
TDK
Retired Moderator
21
Years of Service
User Offline
Joined: 19th Nov 2002
Location: UK
Posted: 23rd Jan 2007 15:18
Quote: "I'm telling you, there's definitely *something* wrong with it somewhere"


I tend to agree, but I think it's with Windows (DirectX?) rather than DB - for a change!

I have a dual 19" FST system and on very rare occasions, I get the 'cannot support this mode' message on the second monitor. I ignore it and the next time the DB program is run it corrects itself.

I was under the impression that when DX initialises, a Windows call minimised any open windows then restored them afterwards.

If it doesn't then you would assume that either DX is screwing up (maybe an incompatibility between DX9 and DX7/8 that DBC was designed to work with), or there's a setting in Windows which you have set differently to me.

TDK_Man

PS: I've made a post in the lounge that requires your advice/input.

Kevin Picone
21
Years of Service
User Offline
Joined: 27th Aug 2002
Location: Australia
Posted: 23rd Jan 2007 16:09 Edited at: 11th Aug 2010 23:08
Rich,

Hmmm, It sounds like when DB exits, it's releasing the surfaces in the wrong order. You might be able to circumvent this by deleting your media manually, prior to exit.

heartbone
21
Years of Service
User Offline
Joined: 9th Nov 2002
Location:
Posted: 28th Jan 2007 18:20
Like TDK I don't get that problem at all.

I use DarkEdit, Win XP SP2 and Win 98 SE.

If I had that problem I would have complained long ago.

I'm unique, just like everybody else.
Richard Davey
Retired Moderator
21
Years of Service
User Offline
Joined: 30th Apr 2002
Location: On the Jupiter Probe
Posted: 28th Jan 2007 19:59
Quote: "Hmmm, It sounds like when DB exits, it's releasing the surfaces in the wrong order. You might be able to circumvent this by deleting your media manually prior to exit."


Sadly it had no effect. I used to code in DBC quite happily in 95, 98 and Win2k, even XP was fine to start with, but something happened (quite a while ago), perhaps a DX change, or a video card driver change, because DBC sure as hell hasn't changed, but it does it consistently now.

Quote: "If I had that problem I would have complained long ago."


It's DB Classic. Complaints are irrelevant. The source was archived a LONG time ago, and will *never* be updated. Ever.

Anyway this issue is moot now as I've moved to Vista and have yet to install DBC as I'm not sure it'll even run at all.

Heavy on the Magick
heartbone
21
Years of Service
User Offline
Joined: 9th Nov 2002
Location:
Posted: 29th Jan 2007 02:45
"long aqo" meant I would have complained back when it mattered.

My feeling is that it's a video driver which is causing the problem.

I'm unique, just like everybody else.
TheSquid
20
Years of Service
User Offline
Joined: 29th Sep 2003
Location: Ohio
Posted: 30th Jan 2007 19:22
I've been using DBC on WindowsXP and I don't experience this problem. I almost always run applications in Windowed mode, rather than full screen, so perhaps there is your workaround.
Latch
17
Years of Service
User Offline
Joined: 23rd Jul 2006
Location:
Posted: 31st Jan 2007 19:39 Edited at: 31st Jan 2007 19:43
@Richard Davey:

I'm not sure if this will help or even applies (Windows 98), but I noticed that when I use DarkEdit, and I open another windows application (especially internet explorer), whenever I run the DBC script and then return to windows, a "fake" application exists on the taskbar without a name. If I click on it, it will disappear - but something is happening that is causing that resource to be triggered.

I noticed a similar thing happening when I used the WIN API to create a menu in a DBC window. Depending on how I use GetMessageA and DispatchMessageA, a new hwnd is returned in struct MSG every time I click on a menu item.



One other thing to maybe consider would be any of the DBC ini settings. Maybe one of those is causing some trouble? The ExternalEditor perhaps? Or maybe even the winsizex and winsizey. Maybe they are resetting all of your other windows inadvertently.



Enjoy your day.
heartbone
21
Years of Service
User Offline
Joined: 9th Nov 2002
Location:
Posted: 31st Jan 2007 20:07
Latch, that "fake application" only happens when you exit a DBC program while in full screen. Upon exiting from a windowed mode, the taskbar tab does not remain.

Maybe this information will help in the understanding.

I'm unique, just like everybody else.
Bluestar4
18
Years of Service
User Offline
Joined: 19th Dec 2005
Location: USA
Posted: 6th Feb 2007 14:21
Hi Richard,
I had a simular experiance when using dark edit. it would move all my icons on the desktop to another position (to where it would fit withing a 640x480 screen ) as far as a work around goes I only had that problem when my screen was in a higher resolution than the programs default(640x480) So I would suggest as a work around that you use the set the display mode command and set it to 1680x1050 so that it doesn't use the default and screw things up as I noticed that when I had set the program I was working on to use the same display as my screen that it no longer done this. perhaps this will work for you as well.

Login to post a reply

Server time is: 2024-04-26 05:31:44
Your offset time is: 2024-04-26 05:31:44