Delphi 2010

[Shannon V. OKeets]

Does anyone know anything about Delphi 2010, or know anyone who knows anything about Delphi 2010?[&:]

All the air in my computer room has been solid blue for the past week.[:@]

[SamuraiProgrmmr]

I haven't installed it yet. Sorry I can't help you.

[SamuraiProgrmmr]

(sorry for double post)

Do you have more specifics---- when are you getting a blue screen, etc. --- I might have an idea of where to look (you never know).

[Shannon V. OKeets]

ORIGINAL: SamuraiProgrammer

(sorry for double post)

Do you have more specifics---- when are you getting a blue screen, etc. --- I might have an idea of where to look (you never know).

My decision this morning - when I woke up - was to deinstall and reinstall Delphi 2010. Who knows, that might help.

===

My best guess is that processing mouse commands for a program (i,e,. MWIF) executing within the debugger confuses the Delphi IDE (Integrated Development Environment). The result is that mouse commands executed when the MWIF has the focus are being intercepted by the IDE, and vice-a-versa. Eventually this get so balled up that neither MWIF nor the IDE respond to any commands (mouse or keyboard). Indeed, at that point it is not possible to minimize or close either program. Only Ctrl-Alt-Delete (which brings up the Win 7 Task Manager) enables them to be shut down.

One certain way to make this happen is fairly simple: I just go up to MWIF's main menu bar and click on one of the drop down menus. That causes every thing to stop working; the drop down menu does not appear.

On the plus side, I am getting very confortable with using C-A-D to kill misbehaving programs. Oh, and restarting Delphi 2010 and MWIF within the IDE takes about 1/20 the time it did on my old machine.

[darune]

Not a delphi programmer, but..

If still causing problems
1) try the release build without running from the IDE/debugger
2) make a minimal program that will reproduce the problem, eventually report it to vendor.

Another guess could be some delphi libraries you are using have been upgraded and changes things.

[Shannon V. OKeets]

ORIGINAL: darune

Not a delphi programmer, but..

If still causing problems
1) try the release build without running from the IDE/debugger
2) make a minimal program that will reproduce the problem, eventually report it to vendor.

Another guess could be some delphi libraries you are using have been upgraded and changes things.

Yes, the Delphi 2010 debugger is still causing me mucho grief.

1 - The MWIF program runs as before as a stand alone app - response to the mouse and keyboard commands are as expected an immediate. It is only when the debugger gets involved that things grind to a halt.
2 - Several minimal programs run just fine. Adding more and more functionality until it breaks is nice in theory but insane to attempt given the size and diversity of the WMIF code (300+ Pascal modules, 150+ forms - all interrelated).
3 - I went through the libraries MWIF uses rigorously and made absolutely sure they are all Win 7 & Delphi 2010 compatible (according to the vendors/authors). For some of the other 'libraries' (collections of Pascal and assembler routines in several units/files) I inherited from CWIF, I went through and eliminated any routines that were not being used. This reduced the simple count of those routines from 433 to 43.

While the above were all good and useful things to do I still have a fundamental probelm with the Delphi IDE. As the simplest case in point, starting the IDE, opening the MWIF app, and then clicking on the IDE's drop down menu item Search causes the IDE to "go away" for 3 to 5 minutes before bringing up the drop down menu item list. During that time the IDE is totally unresponsive, although the mouse can be moved to another app. The 2nd time the Search label is clicked on, the drop down menu appears immediately, as it should have the first time. My conclusion is that something evil is going on.

[Ullern]

ORIGINAL: Shannon V. OKeets

ORIGINAL: darune

Not a delphi programmer, but..

If still causing problems
1) try the release build without running from the IDE/debugger
2) make a minimal program that will reproduce the problem, eventually report it to vendor.

Another guess could be some delphi libraries you are using have been upgraded and changes things.

Yes, the Delphi 2010 debugger is still causing me mucho grief.

1 - The MWIF program runs as before as a stand alone app - response to the mouse and keyboard commands are as expected an immediate. It is only when the debugger gets involved that things grind to a halt.
2 - Several minimal programs run just fine. Adding more and more functionality until it breaks is nice in theory but insane to attempt given the size and diversity of the WMIF code (300+ Pascal modules, 150+ forms - all interrelated).
3 - I went through the libraries MWIF uses rigorously and made absolutely sure they are all Win 7 & Delphi 2010 compatible (according to the vendors/authors). For some of the other 'libraries' (collections of Pascal and assembler routines in several units/files) I inherited from CWIF, I went through and eliminated any routines that were not being used. This reduced the simple count of those routines from 433 to 43.

While the above were all good and useful things to do I still have a fundamental probelm with the Delphi IDE. As the simplest case in point, starting the IDE, opening the MWIF app, and then clicking on the IDE's drop down menu item Search causes the IDE to "go away" for 3 to 5 minutes before bringing up the drop down menu item list. During that time the IDE is totally unresponsive, although the mouse can be moved to another app. The 2nd time the Search label is clicked on, the drop down menu appears immediately, as it should have the first time. My conclusion is that something evil is going on.

I'll guess that new versions of your developer's software will mimic Windows style windows behavior more closely than before. If MWIF overrides any windows command that have changed with the new versions, would this cause trouble?

[Shannon V. OKeets]

ORIGINAL: ullern

ORIGINAL: Shannon V. OKeets

ORIGINAL: darune

Not a delphi programmer, but..

If still causing problems
1) try the release build without running from the IDE/debugger
2) make a minimal program that will reproduce the problem, eventually report it to vendor.

Another guess could be some delphi libraries you are using have been upgraded and changes things.

Yes, the Delphi 2010 debugger is still causing me mucho grief.

1 - The MWIF program runs as before as a stand alone app - response to the mouse and keyboard commands are as expected an immediate. It is only when the debugger gets involved that things grind to a halt.
2 - Several minimal programs run just fine. Adding more and more functionality until it breaks is nice in theory but insane to attempt given the size and diversity of the WMIF code (300+ Pascal modules, 150+ forms - all interrelated).
3 - I went through the libraries MWIF uses rigorously and made absolutely sure they are all Win 7 & Delphi 2010 compatible (according to the vendors/authors). For some of the other 'libraries' (collections of Pascal and assembler routines in several units/files) I inherited from CWIF, I went through and eliminated any routines that were not being used. This reduced the simple count of those routines from 433 to 43.

While the above were all good and useful things to do I still have a fundamental probelm with the Delphi IDE. As the simplest case in point, starting the IDE, opening the MWIF app, and then clicking on the IDE's drop down menu item Search causes the IDE to "go away" for 3 to 5 minutes before bringing up the drop down menu item list. During that time the IDE is totally unresponsive, although the mouse can be moved to another app. The 2nd time the Search label is clicked on, the drop down menu appears immediately, as it should have the first time. My conclusion is that something evil is going on.

I'll guess that new versions of your developer's software will mimic Windows style windows behavior more closely than before. If MWIF overrides any windows command that have changed with the new versions, would this cause trouble?

It's not clear to me what you mean by your first sentence. MS Windows' user interface 'behavior' changes with every new operating system MS releases (perhaps more often).

From my point of view there are multiple black boxes (operating system, compiler, 3rd party software packages) doing stuff in series (perhaps with feedback loops) that could potentially be a cause of the problems I am experiencing running the program with the Delphi 2010 debugger/IDE.

After another day of not making any noticable progress, I'm going to reinstall Delphi 2010 - with the hope that the 3rd time's the charm. My motivation for this is that I currently am getting a fatal error from the compiler when I request a compile of all the modules in MWIF. It does the first 124,000 lines without complaint and then fails. If I restart it where it failed, it completes without complaint (352,000 lines). But everytime I start a full compile (a complete build of the EXE) I get the same fatal error in the compiler at the same place. In fact, I have to use Ctrl-Alt-Del to kill Delphi 2010's IDE at that point. Compiler's are not suppose to fail fatally when commanded to compile a series of files - even if there are 300+ of them.