MyTetra Share
Делитесь знаниями!
Annoying 'window resize' bug - anyone found a fix?
Время создания: 23.06.2018 08:24
Текстовые метки: dark basic classic window resize bug
Раздел: Dark Basic


FORUM HOMESEARCHPROFILEMESSAGES (0)MY THREADSLOGOUT

developer forums Banner image

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

Author

Message


Richard Davey

16 YEARS OF SERVICE

User Offline

Joined: 30th Apr 2002

Location: On the Jupiter Probe

Earn Badges

Posted: 23rd Jan 2007 23:15 Link

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

12 YEARS OF SERVICE

User Offline

Joined: 26th Dec 2005

Location:

Earn Badges

Posted: 24th Jan 2007 01:07 Edited at: 24th Jan 2007 01:07 Link

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

16 YEARS OF SERVICE

User Offline

Joined: 30th Apr 2002

Location: On the Jupiter Probe

Earn Badges

Posted: 24th Jan 2007 01:23 Link

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

12 YEARS OF SERVICE

User Offline

Joined: 26th Dec 2005

Location:

Earn Badges

Posted: 24th Jan 2007 01:37 Link

Quote: "Nah, it doesn't work."



really? it does seem to work when i do it


i like pancakes..

TDK

15 YEARS OF SERVICE

User Offline

Joined: 19th Nov 2002

Location: UK

Earn Badges

Posted: 24th Jan 2007 01:44 Link

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

16 YEARS OF SERVICE

User Offline

Joined: 30th Apr 2002

Location: On the Jupiter Probe

Earn Badges

Posted: 24th Jan 2007 01:50 Link

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

15 YEARS OF SERVICE

User Offline

Joined: 19th Nov 2002

Location: UK

Earn Badges

Posted: 24th Jan 2007 02:18 Link

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

15 YEARS OF SERVICE

User Offline

Joined: 27th Aug 2002

Location: Australia

Valued Member

Earn Badges

Posted: 24th Jan 2007 03:09 Edited at: 12th Aug 2010 10:08 Link

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.



New PlayBasic Learning Edition Released 24th April 2010

heartbone

15 YEARS OF SERVICE

User Offline

Joined: 9th Nov 2002

Location:

Earn Badges

Posted: 29th Jan 2007 05:20 Link

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

16 YEARS OF SERVICE

User Offline

Joined: 30th Apr 2002

Location: On the Jupiter Probe

Earn Badges

Posted: 29th Jan 2007 06:59 Link

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

15 YEARS OF SERVICE

User Offline

Joined: 9th Nov 2002

Location:

Earn Badges

Posted: 29th Jan 2007 13:45 Link

"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

14 YEARS OF SERVICE

User Offline

Joined: 29th Sep 2003

Location: Ohio

Earn Badges

Posted: 31st Jan 2007 06:22 Link

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

11 YEARS OF SERVICE

User Offline

Joined: 23rd Jul 2006

Location:

Earn Badges

Posted: 1st Feb 2007 06:39 Edited at: 1st Feb 2007 06:43 Link

@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.



typedef struct {

HWND hwnd;

UINT message;

WPARAM wParam;

LPARAM lParam;

DWORD time;

POINT pt;

} MSG, *PMSG;

+ Code Snippet

1

2

3

4

5

6

7

8

typedef struct {

HWND hwnd;

UINT message;

WPARAM wParam;

LPARAM lParam;

DWORD time;

POINT pt;

} MSG, *PMSG;



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.



[SETTINGS]

TextLanguage=English

TextLanguage-Charset=1

HelpLanguage=English

HelpLanguage-Charset=1

HelpFontSize=0

ExternalEditor=None

blitflipmode=1

vbcreate=0

vbusage=0

3doverlay=0

runtimetest=1

tracemode=0

windowmode=0

popupoff=0


; Test and Trace Settings

; ----------------

; runtimetest: 0=simple error reporting / 1=advanced error reporting

; tracemode: 0=no trace information / 1=produce trace files


; Compatabilitiy Settings

; ----------------

; windowmode: 0=no window / 1=run in window

; blitoverdraw : 0=normal / 1=Draw All 2D twice

; blitflipmode : 0=double videomem flip / 1=blit to video memory

; runtimetest : 0=no extra error data / 1=produce extra error data

; vbcreate : 0=normal / 1=WriteOnly / 2=No Clip / 3=[1]+[2] / 4=SystemMem

; vbusage : 0=normal / 1=Wait / 2=WriteOnly and Wait / 3=SurfaceMem and Wait

; 3doverlay : 0=normal / 1=Utilize ZBuffer Clear for overlapped 3D rendering


; StartUp Settings

; ----------------

; Use a SETUP.INI file with the [STARTUP] keys below to

; control the initial state of your application:-

; eg. window=1 will start your app in a window


[STARTUP]

window=0

winposx=0

winposy=0

winsizex=640

winsizey=480

+ Code Snippet

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

[SETTINGS]

TextLanguage=English

TextLanguage-Charset=1

HelpLanguage=English

HelpLanguage-Charset=1

HelpFontSize=0

ExternalEditor=None

blitflipmode=1

vbcreate=0

vbusage=0

3doverlay=0

runtimetest=1

tracemode=0

windowmode=0

popupoff=0

; Test and Trace Settings

; ----------------

; runtimetest: 0=simple error reporting / 1=advanced error reporting

; tracemode: 0=no trace information / 1=produce trace files

; Compatabilitiy Settings

; ----------------

; windowmode: 0=no window / 1=run in window

; blitoverdraw : 0=normal / 1=Draw All 2D twice

; blitflipmode : 0=double videomem flip / 1=blit to video memory

; runtimetest : 0=no extra error data / 1=produce extra error data

; vbcreate : 0=normal / 1=WriteOnly / 2=No Clip / 3=[1]+[2] / 4=SystemMem

; vbusage : 0=normal / 1=Wait / 2=WriteOnly and Wait / 3=SurfaceMem and Wait

; 3doverlay : 0=normal / 1=Utilize ZBuffer Clear for overlapped 3D rendering

; StartUp Settings

; ----------------

; Use a SETUP.INI file with the [STARTUP] keys below to

; control the initial state of your application:-

; eg. window=1 will start your app in a window

[STARTUP]

window=0

winposx=0

winposy=0

winsizex=640

winsizey=480



Enjoy your day.

heartbone

15 YEARS OF SERVICE

User Offline

Joined: 9th Nov 2002

Location:

Earn Badges

Posted: 1st Feb 2007 07:07 Link

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

12 YEARS OF SERVICE

User Offline

Joined: 19th Dec 2005

Location: USA

Earn Badges

Posted: 7th Feb 2007 01:21 Link

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.


Bluestar4~

http://www.geocities.com/bluestar4games

This thread has not been posted in for more than 90 days and has been locked!


Server time is: 2018-06-23 04:16:18

Your offset time is: 2018-06-23 15:16:18

© Copyright 2018

Acceptable Usage Policy

Так же в этом разделе:
 
MyTetra Share v.0.53
Яндекс индекс цитирования