TjsDialog: Release Info and Demo Application
The TjsDialog component is almost ready for release and here is your opportunity to try one of the demo applications that will ship with the component.
How much does it cost?
Currently on BDS 2006 is supported. This includes the Turbo products. Delphi6, 7 and 2005 will also be supported with the full release version, as will a VCL.NET under BDS 2006.
The free version will not work with VCL.NET. You must purchase the full version to use with VCL.NET.
NOTE: This dialog does NOT currently wrap the official TaskDialog and TaskDialogIndirect API functions on Vista.
While this is planned as a free update to the dialog functionality, some options cannot be emulated by the official Vista API functions.
The importance of this feature will be determined by users.
How much does it cost?
- The component costs 40 Euros per developer.
- There is no site license available. If you require more than 20 licenses, contact me for pricing.
- share-it link for purchase.
- If you would prefer to use PayPal then you need to contact me before purchasing (helps to minimize false payments).
- Full source
- Additional controls used by the dialog
- TjsDialog specific component editors
- Priority support
- Download exe-demo of TjsDialog. The demo zip file contains 2 files. The executable (TjsDialogDemo.exe) as well as a warning.rtf file. The demo requires this file for one of the dialogs.
- Currently being worked on.
Currently on BDS 2006 is supported. This includes the Turbo products. Delphi6, 7 and 2005 will also be supported with the full release version, as will a VCL.NET under BDS 2006.
The free version will not work with VCL.NET. You must purchase the full version to use with VCL.NET.
NOTE: This dialog does NOT currently wrap the official TaskDialog and TaskDialogIndirect API functions on Vista.
While this is planned as a free update to the dialog functionality, some options cannot be emulated by the official Vista API functions.
The importance of this feature will be determined by users.
posted by JED at 12:39 AM
9 Comments:
Hi Jeremy,
perhaps you're interested in a few "gotchas" I've noticed in the demo:
- in dialogs with expandable details (e.g. "A bit of everything", "Custom Buttons" etc.), toggling Details loses the checked state of the checkbox
- in the "Header" dialog, after toggling Details, the footer text is displayed over a part of the footer icon
- the "Information" icon in the footer of some dialogs ("Custom Buttons", "Compare Dialog") doesn't look right (white used as transparent color?)
- the marquee progress bar movement should probably be smoother and with less flickering
- clicking on bottom-rightmost "Close Progress Window" button causes an A/V when no progress window is displayed ;-)
I've tried the demo on Windows 2000 SP4.
I think this is a great idea for a component, I'm sure it will be very useful to anyone who wants to support the new Vista UI.
Nice work, I wish you a lot of success!
All I can say is wow! We sat here trying the demo on Vista and XP, worked great!
Looks promising, Jeremy! Could you post some screenshots that compare native vista dialogs to your emulation, please?
Comments inline
- in dialogs with expandable details (e.g. "A bit of everything", "Custom Buttons" etc.), toggling Details loses the checked state of the checkbox
Thanks. Fixed
- in the "Header" dialog, after toggling Details, the footer text is displayed over a part of the footer icon
Fixed
- the "Information" icon in the footer of some dialogs ("Custom Buttons", "Compare Dialog") doesn't look right (white used as transparent color?)
These are resized form the original 32x32 Icons. I'll see what I can do without embedded specific 16x16 versions. Note you can set the Footer glyph with a property and use your own icon if you wanted to.
- the marquee progress bar movement should probably be smoother and with less flickering
Yes, it needs a little work.
- clicking on bottom-rightmost "Close Progress Window" button causes an A/V when no progress window is displayed ;-)
Ah, fixed.
> I think this is a great idea for a > component, I'm sure it will be
> very useful to anyone who wants to > support the new Vista UI.
Thanks. It is important to note that you can set the dialog color to be clBtnFace (hide the button divider) and they wouldn't look out of place of Win2000 or XP systems either. There are many properties to play around with.
> Nice work, I wish you a lot of
> success!
Thanks, me too!
Appreciate your feedback.
If you want to try a release candidate, send me an email.
Demo has been updated with these fixes (plus a few others).
Thanks Vincent.
Anon - I'll see what I can do.
Hi,
From all the TaskDialog components I've tested so far, this seems to be the best. I've got a few things that would make it even closer to the Vista original:
The close button in the title bar (the red x) should only be visible if there is a Cancel button in the dialog or if AllowCancel = True.
There should not be a focus rect for command link buttons when the user clicks a button, unless the focus rect was already visible before.
Please add acceleration keys for buttons like "Yes" or "No". A user should be able to press "Y" or "Alt+Y".
When a user presses Ctrl+C, the text of the dialog including the buttons, ... should be copied to the clipboard. Try this with the original Vista Task Dialog or any other Delphi Message Dialog to see what it looks like. This is very helpful when a user wants to send an error message to me.
And one more thing:
On my PC, the "Segoe UI" font only looks good when ClearType is enabled. If a user installs Office 2007 on XP they will have this font installed. Can this font easily be changed to "Tahoma" or "MS Shell Dlg 2"?
> The close button in the title bar (the red x) should only be visible
> if there is a Cancel button in the dialog or if AllowCancel = True.
Currently you can set the BorderIcons directly. An AllowCancel property
will also be introduced, as well as an AllowMinimize property.
> There should not be a focus rect for command link buttons when the user
> clicks a button, unless the focus rect was already visible before.
I will look into this and make the necessary changes
> Please add acceleration keys for buttons like "Yes" or "No".
Will be done in the next update
> When a user presses Ctrl+C, the text of the dialog including the buttons,
> ... should be copied to the clipboard.
This will definitely be done.
> And one more thing:
> On my PC, the "Segoe UI" font only looks good when ClearType is enabled.
> If a user installs Office 2007 on XP they will have this font installed.
> Can this font easily be changed to "Tahoma" or "MS Shell Dlg 2"?
You can change the Font to be anything you like for each section of the font.
Some sections do use the same font source for there font properties though.
Example the Content Font is used for the Verification check box and the
command buttons font.
There is also the ability to setup the default font used for each section
so you don't have to continually change it. You would just do a call as such
once in your application.
// this will change the font used by the dialog content section
lMyFont := TFont.Create;
try
lMyFont.Name := 'Tahoma';
lMyFont.Size := 12;
lMyFont.Style := [fsUnderline];
SetDefaultFont(ctContent, lMyFont);
finally
lMyFont.Free;
end;
There is also a demo application that shows how to setup and modify the fonts used by the dialog.
The demo download link is broken...
Is there any download link to the trial version?
Looks great and I'm eager to try it out!
Later,
Fernando Madruga
> The demo download link is broken...
Opps. My ISP was have some hard disk issues and it got deleted.
I have reposted the demo but this version is build with the newest version of the component. The version that will go out to registered users this week as the first update.
> Is there any download link to the > trial version?
This will be made available later this week or early next week.
Sometime before the 15th of January I hope.
Thanks for your interest.
Post a Comment
<< Home