Suggestion: Multiple suggestions, read topic
Oldorf
Copenhagen Denmark
Hi guys!
First a small rename request !
- The new property ReportAutor, shouldn't it have been ReportAuthor ?
I have two suggestions for FastReport !
1.
When the report is password protected, the FR automatically shows
a password dialog, this is great but some situations require that it doesnt.
I made for myself a boolean variable in the fr_class.pas unit called
frProtectByFR, when FR is to fire the dialog I check to see if the frProtectByFR
is set to false if it is it skips the dialog.
This makes it possible for me to show a list of reports and load their names
and description, when the user then wants to edit the report I query the user
for the password.
My suggestion would be
-A set of protection types e.g. protect on: load, save, print as a property.
-And/or a OnProtection event.
-And/or a boolean Autoprotect property.
2.
When exceptions occur in FR dialogs are forced on the screen, leaving the
programmer no option to overrule the exception handling, it's okay that FR
loads resource strings to be shown but it should re raise the exception since
a exception dialog will appear if the programmer didn't overrule it.
I have made a variable in the fr_class.pas that is checked when an exception
occur, but it's a bad way to do it !
My suggestion would be
- make the exception real exception.
- if necessary alter the e.message so it contains the necessary resouce strings.
Reggies
Oldorf
First a small rename request !
- The new property ReportAutor, shouldn't it have been ReportAuthor ?
I have two suggestions for FastReport !
1.
When the report is password protected, the FR automatically shows
a password dialog, this is great but some situations require that it doesnt.
I made for myself a boolean variable in the fr_class.pas unit called
frProtectByFR, when FR is to fire the dialog I check to see if the frProtectByFR
is set to false if it is it skips the dialog.
This makes it possible for me to show a list of reports and load their names
and description, when the user then wants to edit the report I query the user
for the password.
My suggestion would be
-A set of protection types e.g. protect on: load, save, print as a property.
-And/or a OnProtection event.
-And/or a boolean Autoprotect property.
2.
When exceptions occur in FR dialogs are forced on the screen, leaving the
programmer no option to overrule the exception handling, it's okay that FR
loads resource strings to be shown but it should re raise the exception since
a exception dialog will appear if the programmer didn't overrule it.
I have made a variable in the fr_class.pas that is checked when an exception
occur, but it's a bad way to do it !
My suggestion would be
- make the exception real exception.
- if necessary alter the e.message so it contains the necessary resouce strings.
Reggies
Oldorf
Comments
1.
A class that contains the properties/info of the report:
? ? TReportProperties= class(TObject)
? ? ? ? Name: String;
? ? ? ? Author: String;
? ? ? ? ReportType: TfrReportType;
? ? ? ? PasswordProtected: Boolean;
? ? ? ? Password: String;
? ? ? ? VersionMajor: String;
? ? ? ? VersionMinor: String;
? ? ? ? VersionRelease: String;
? ? ? ? VersionBuild: String;
? ? ? ? Comment: String;
? ? ? ? CreateDate: TDateTime;
? ? ? ? LastChange: TDateTime;
? ? ? ? FilePath: String;
? ? End;
And a function to only load that info for display purposes.
Reggies
? ? ? ? Oldorf