Resetting to 'Normal.RTF' does not work

[pocketom]

This RTF Generator is too funny. When choosing File/Update Styles, the dialog asks if you want to import the standard styles from normal.rtf located in the EA doc templates folder. I imported the unmodified original normal.RTF. Half of the styles are then in the original state afterwards (e.g. heading 1, 2,... are blue again and so forth...). But other styles keep (especially this TOC styles seem to have burnt in somewhere).

Who did all that offroad implementation?

Sorry for the critics EA guys, but that's really a shame., The behavior of the RTF template editor is a very weird thing overall. I can't create so much bug reports, even if I'd like too. That's only the tip of the iceberg, and I guess you know that. Why are so few people talking about that?

I want answers guys!

[mrf]

If you want answers from Sparx, please go through the official channels and log a bug/support request through the link below.

Please note the forum is a user forum, not an official support channel (it just happens that some Sparx employees frequent it!).

[pocketom]

Hi Michael,

I understand your point. But I hope you also understand mine. As said, I wouldn't try to estimate how many bug reports would be necessary here because it seems like the RTF editor never passed any testing stage. Customers that already paid for the product are not in charge here (not to be confused with regular frequently occurring bugs, here we are all in charge!). And I'm sure that the quality delivered with the RTF editor module isn't comparable in any way to all the other modules in EA 8. In general EA is great tool for me, but forgive me repeating - it's an eyesore potentially damaging EA's overall reputation. I believe that this can be discussed publically now.

So from my feeling this module should be just rewritten from scratch because it's already over-engineered in my opinion. What I can do is writing an official letter to AU, proposing exactly what I've written. But I'm not sure if this has a chance to be accepted at the moment. I'm pretty sure that nothing much will happen until users increase pressure significantly. That's the usual way, unfortunately.
Therefore I want to collect a bit more user feedback first. Let's see if reporting capabilities are really as important as it's praised.

Thanx for understanding,
Thomas

[mrf]

Yes we do understand your point, and we are always working on and improving the RTF reporting framework. I think the thing that makes it tricky from a development perspective is that everyone expects something different from the reporting mechanism:

- Everyone is providing different input
- Everyone's expectations of the output that is generated is different

Providing a tool that is generic, yet usuable at the same time, is a very hard nut to crack, more often than not the more generic you make it, the less usable it is (and vice versa). So we're trying navigate that fine line as best we can, and we appreciate your feedback.

We're currently experimenting with a different approach to RTF reporting. If it's mature enough it should be included in the beta of the next major build and we'll gauge the communities reaction from there.

[pocketom]

Thanx for your reply. I'm looking forward to a new reporting tool. Once available I'll test it and post my feedback in the forums.

[RoyC]

By all means post your comments and findings on the forum for other users to see.

However, Sparx Systems has a number of official channels (bug reports, feature requests, beta feedback and direct email to Sparx Support) for providing comment on its products. Using these channels ensures that your reports are recognized, logged, passed to the correct technical authority and, as far as is possible, resolved and responded to.

[Happy]

About the main problem in this discussion:

Update Styles does all but not completely reset the template where it is updated into.

Maybe deleting all styles via "Edit Style..." will do the job ... .

But I'm not sure.

[pocketom]

Ok, you mean first deleting the build in styles then import from normal.rtf or afterwards? I'm not sure, to test I need to extract my project first from SQL DB back into a Jet4 eap file. I'm a bit scared to mess it up finally  

[Happy]

Always use a backup and only test on copies of templates.

And don't hesitat to make copies often when trying new features ... .

In fact deleting existing styles leaves a mess when those styles are used within the template ... tried myself.

Actually I think the only way through the errornous update of styles is to check every line of text within the template (only a few pages ...), and change errors manually where they occur.