readme- txt rtf problem

Rulan · Postby **Rulan** » Fri Dec 21, 2012 2:40 am

Hi,
The setups work fine.. We had a problem with the load of readme or licence in txt or rtf to screen.

First we use the theme "glass" and IA 15.. and there was no chance to get the txt/rtf file to the screen at setup-time.

-First we had to rename the readme control in the readme-dialog to "readmetxt".
then we tried to get load, but no success.
-Then we copy both readme.rtf and readme.txt to the code-directory with no success.
-Then we save the readme.rtf as NORMAL ".TXT" format with the extention ".rtf"to disk and with have success, the readme is shown
-We edit the readme inside IA, it will be getting funny... Only rtf is changed but txt is show on screen, because our changes are not shown and the changes are only made to rtf. And rtf is now an rtf-format with tabs-formats and the changes are only made to rtf, not to txt.
It seems IA tried to show txt and made changes to rtf...

We do the following I made changes with editor to the txt file. on scrren in IA we see the rtf-file. We made a build and then we see the changes made to txt with the editor but in IA (in Eula and ReadMe-Editor) we see the old rtf-file content.
-the Screen txt.text is not nicely formatted; some tabs are shown correctly so the nice looking text from the original is not presented to screen exactly.

It seems to me, that there is confusion between rtf and txt.
rtf cannot be used for build, but the rtf-files has to be physical in the code directory.

Do we something wrong? is it a bug?
regards

Postby **FrancescoT** » Fri Dec 21, 2012 8:41 am

Dear Rulan,

the Glass dialog theme uses the Memo control to display the License and the Readme file.
This controls can render a text file only. You should use a RichEdit control for RTF files.

For an example on how to use a RichEdit control to display a RTF file, please refer to the Official dialog theme.
The Official dialog theme uses glass effect as well, but limited to the top dialog area, in order to improve the render capability of the RichEdit control.

Also note, that you must update the License & Readme files under the project directory or you must include into the Supportfiles, those files each time you modify them.

Regards.

Rulan · Postby **Rulan** » Fri Dec 21, 2012 9:40 am

Thanks,
I will try to use RichEdit element...

But I think, that it is not normal to see in "EULA and Readme" the content of rtf file und when you edit there, the changes are saved only to the txt-file. :cry:

and after the build you see the rtf- with no changes.

regards

Postby **FrancescoT** » Fri Dec 21, 2012 12:06 pm

Dear Rulan,

honestly, I'm really not quite sure to full understad you when;

But I think, that it is not normal to see in "EULA and Readme" the content of rtf file und when you edit there, the changes are saved only to the txt-file. and after the build you see the rtf- with no changes.

Can you send me a sample or can yuo try to clarify it?

Regards

Rulan · Postby **Rulan** » Thu Dec 27, 2012 1:53 am

Hi,
well, I will try to explain...

1) there are 2 files which exist in IA source directory... a readme.txt + a readme.rtf
2) You make changes in IA's "EULA and Readme" in the readme-section... (by the way you see the content of readme."rtf")
3) Changes were physically written to readme.rtf
4) But after the build when you run setup you see the content of the old readme.txt
5) and when you change the content of the txt-readme with an editor, make a new build, you see the changes made in readme.txt in the new setup...

strange, isn't it? :roll:

regards

Postby **FrancescoT** » Thu Dec 27, 2012 5:37 am

Dear Rulan,

Ye it is, but are you are really sure you are updating the same RTF file used by your project?
I just tried and with my test works correctly.

Regards

Rulan · Postby **Rulan** » Thu Dec 27, 2012 6:02 am

I am sure,
workaround is theme glass and memo-element in readme-dialog... with richedit saving in rtf is ok...

but perhaps I am crazy...

And I have tried with richedit-element a build, but I have optical problems to read the readmefile, because it is unreadable...
I tried to set the colors, but that has no effects. Is it a problem with theme glass?
But look self:

: Readme_glass.png (130.34 KiB) Viewed 10475 times

1) is memo field which works with txt
2) is richedit field which works with rtf
and I put a small projekt inside to have a look
regards

Postby **FrancescoT** » Thu Dec 27, 2012 8:41 am

Dear Rulan,

As I said with my first reply;

The Official dialog theme uses glass effect as well, but limited to the top dialog area (Only), in order to improve the render capability of the RichEdit control.

Unfortunately, there are text readability problems with RichEdit control if used with glass effect not applied to a limited dialog area.

Regards

Rulan · Postby **Rulan** » Thu Dec 27, 2012 9:20 am

???? confused...
Are You looking for a solution?

so it is not possible to use licence/readme.rtf and licence/readme.txt with glass theme? !!! ".TXT" and memo is also not useable because of the problem with rtf and txt confusing-saving, I told before?

Now I have to find a new theme for all our setups we did before? This means much efforts until now for nothing?

Why You have "glass" in your basic theme-selection?

Is there no workaround?
regards

Postby **FrancescoT** » Thu Dec 27, 2012 11:22 am

Dear Rulan,

I try to explain it once again.

The RichEdit control can be used with glass effetcs, but having care to apply the effect to a limited dialog area.
This is not an InstallAware limitation but depend on how the control paints its client area.

Now I have to find a new theme for all our setups we did before? This means much efforts until now for nothing?

No, because you can easly modify your glass effect apparence to be applied to a limited dialog area. Please have a look at the attached sample project.

Why You have "glass" in your basic theme-selection?

In fact, the FULL glass effect dialog theme doesn't use the RichEdit control but the Text Memo instead ( ... that correctly displays a text file as I verified previously ... see my reply).