[REQ] Replace MessageBox'es with usual dialogs

[Flint]

I have an idea: why should TC use standard Windows MessageBox if there are so many problems with it? Why not create usual dialog resources and use them instead? There's not so much work, but it would fix the following problems:
1. Non-working Enter and Tab in main window when a message box is shown in Lister or CbC.
2. Non-translatable OK/Cancel/etc buttons (and at least some of the TC translators would be very happy to see such an improvement ).
3. Non-working Esc key in message boxes of Yes/No type.
4. It will be easy to add new controls into these dialogs (like e.g. a checkbox "Do not show this dialog again").
5. The font in these message boxes will become TC-controllable instead of Win-controllable.

[Clo]

2Flint

Hello K. !

• Indeed I support strongly that suggestion and agree all points, since I expressed the same n… times,
specially in the beta-test forum, like you know certainly !

…(and at least some of the TC translators would be very happy to see such an improvement )…

• Count me in that herd !

 FR
Claude
Clo

[petermad]

Count me in too

[Alextp]

Support, it will be useful.

[ghisler(Author)]

TC uses the standard MessageBox wherever possible because it uses the standard icons of the underlying system, so the user sees what he is used to see. There is no problem with MessageBoxes as long as you don't keep them open too long and try to do other things while they are open.

[Alextp]

2ghisler(Author)
No problem to draw standard icons in your own programs.
See how I do it in TC Plugins Manager:

Code: Select all

  TFormInstallLog = class(TForm)
  ...
    ImageInfo: TImage;
    ImageErr: TImage;
  ..

procedure TFormInstallLog.FormShow(Sender: TObject);
begin
  ImageInfo.Picture.Icon.Handle:= LoadIcon(0, IDI_ASTERISK);
  ImageErr.Picture.Icon.Handle:= LoadIcon(0, IDI_EXCLAMATION);
end;

[Flint]

There is no problem with MessageBoxes as long as you don't keep them open too long and try to do other things while they are open.

To the contrary, see pp.2-5 from the first post - they are always problems, no matter how long the message box is open.

[Clo]

2Flint

Hello K. !

• Naturally… With a simple "Warning", see an old EXAMPLE about the fonts… and the awful [OK] not translatable.
- The blue word "Erreur" shows the real expected painting, the lower image shows how it might look for the whole.
- Dated May, 5th. 2006 from a thread I started in the beta-forum (quickly buried).

ghisler(Author) wrote

TC uses the standard MessageBox wherever possible because…

… that saved a few bytes in the old versions, in the goal : 
"Fit in the Holy Diskette", it's just a remnant of that era, IMHO…
- There are a few types of such messages, so I assume it's not a big deal to add them in the resources.
- A similar one is only a ten-line script in C++ (including a tick-box "Don't display anymore…").
Delphi is more verbose, but not a lot for that.

 FR
Claude
Clo

[Vansumsen]

Hello !

- Also, I would prefer that TC uses its own messages, so I support the Flint's proposal !

Friendly

Paul

[Alextp]

- A similar one is only a ten-line script in C++
Delphi is more verbose, but not a lot for that

Yes, Delphi resource would be larger, but not too large. Maybe 1-2K,
not larger imho...

[Sosna]

support ++

[Motorocker]

Support.
Maybe Total can show simple MessageBox[OK] dialogs in tray like SM2BT or KillOK?

P.S. I can't use Total without KillOK Click, click, click, again click, click... ufff!

[Flint]

Maybe Total can show simple MessageBox[OK] dialogs in tray like SM2BT or KillOK?

Oh, no! Anywhere, but not in tray!!!

[D1P]

Support Flint suggestion.

[CoolWater]

Isn't Alextp's suggestion a good alternative??

http://ghisler.ch/board/viewtopic.php?t=17593

Regards,
CoolWater