Issue Details (XML | Word | Printable)

Key: FDT-1336
Type: Improvement Improvement
Status: Confirmed Confirmed
Priority: Major Major
Assignee: FDT Team
Reporter: Malte Beyer
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
FDT

Reset compiler when unicode range of embeded font changes

Created: 21/Sep/10 02:45 PM   Updated: 22/Jun/12 06:42 PM
Component/s: Launching
Affects Version/s: FDT 4.5.2
Fix Version/s: FDT
Security Level: public

Time Tracking:
Not Specified

Review Type: Review by Product Owner


 Description  « Hide
When using [Embed] for embedding fonts you can define a unicode range of characters, which should be embedded.

The problem: when changing the unicode range and recompiling, the compiler does not manage this change. For the compiler nothing has changed. So it won't compile the change of the unicode range. You have to reset the compiler manually to see the change. This is very confusing and frustrating for the user.

After speaking with Steffi and Meinhard they said, that FDT could reset the compiler automatically when the unicode range has changed. This would be a great improvement! Change the unicode range, compile with the launcher and everything works just as expected.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Alan K (Deprecated) added a comment - 13/Dec/10 02:04 PM
We looked into this and having the compiler reset automatically could end up causing more problems. There doesn't seem to be any easy answer for this.

Suppose we have FDT automatically reset the incremental compilation - this could really slow things down if you have a large project. The trick is also to determine when to do the resetting - how would we know when you were 'done' editing the unicode range.

Imagine this scenario:

1. I make one change
2. FDT resets the compiler
3. i make another change
4. FDT resets the compiler
5. I made a mistake and have to redo something
6. FDT resets the compiler

Or is it just easier for the user to remember to flush the compiler when he needs to - like with a web browser.


Malte Beyer added a comment - 13/Dec/10 05:46 PM
How about showing a popup when you determine that the user has changed something regarding unicode range? A popup which tells the user: "hey, whenever you change something at the unicode range, don't forget to reset the compiler!"". This popup can be shown only once and never again. But it will help the user to understand what is going on. Just an idea ...