Hexara

Thank you so much! It's a bit too much complicated but I figured it out at last, thank you for fixing the file and uploading it as well, it helped me a lot to better understand the instructions.

This document has a number of issues.
Place the text cursor in the body text frame. Using the Text Styles panel, click the menu icon to the right of the numbered Heading 1 style and choose Edit. Click Bullets and Numbering in the left pane. In the Text field, remove the trailing space. Maybe you wanted it there for some reason but it's messing up the TOC's heading indent. Click OK. Place the text cursor in the TOC heading text. Using the TOC panel, click the menu icon to the right of Heading 1, Heading 2, and Heading 3 in the list of text styles at the bottom. It will open a popup window. For Heading 1, change Indent Level to 1. For Heading 2, change it to 2 and select Include Page Number. For Heading 3, change it to 3 and select Include Page Number. Using the Text Styles panel, click the menu icon to the right of TOC 1: Heading 1 and choose Edit. You deleted the original tab stop when adding the new one. First, the new one is too narrow at 3mm, that is narrower than the A. before Heading. Click in the text field and make it wider, perhaps 10mm or 3p. I imagine you followed the instructions to set it to 3p but your test document was mm and you just typed 3 instead of 3p. Click the Add New Tab Stop button below the list - the new one will default to 6mm in this document. Change it to 0. Click the alignment (the next control) and change it to Right. Click the ellipsis control and select "From Right". Click OK - these steps will fix the heading 1 entries in the TOC. Click the menu icon to the right of TOC 1: Heading 2 and choose Edit. For this one you changed the existing 0 tab to 194mm and made it left aligned but it's still "From Right". Change it to 0 and Right aligned. Click the Add New Tab Stop button below the list - the new one will default to 6mm in this document. Make this one 10mm or whatever you want.  Click OK Click the menu icon to the right of TOC 1: Heading 2 and choose Edit. For this one you changed the existing 0 tab to 137mm but it's still right aligned and "From Right". Change it to 0. Click the Add New Tab Stop button below the list - the new one will default to 12.7mm in this document. Make this one 10mm or whatever you want.  Click OK Here's the fixed test document.
Good luck.
ASSETS.afpub

Please refer to "Using numbered headings in a table of contents" on page 81 of the manual I shared in the forum, you can find it in the link in my signature. In short, you have to add another tab stop.

Edit the Heading 3 text style (not TOC 1: Heading 3), click Style on the left, and select Sub-heading from Next Level. The Next Level field controls the text style hierarchy.

Pretty sure it doesn't understand anything.
Most common screw up / mistake / confusing thing in the ToC is that the layer position is important, not the place on the page.
Look at your layers panel and move three different text frames up or down. Regenerate the ToC after each move. Note that the different text layers will move in the ToC.
Bottom is the first layer for the ToC ordering, top is the last layer for ToC ordering.

Use a different Paragraph Style spacing for the Heading  and sub-heading. Note that I changed the font for the TOC 1: Book Name in one but not the other screen shot.

 

 

First of all, I would like to express my great disappointment, I know that a great portion of people here may disagree with me.
Just imagine how it happened:
1. Release version 1
2. Users request tons of essential features, for me, mainly RTL support which is ESSENTIAL
"AWARD WINNING" software in "2022", and still no RTL support, I can't figure out how I paid for a software that can't type in Arabic lol
3. Release tons of updates with more bugs and glitches appearing every update
4. Fix bugs, new bugs appear
5. Development team is done with those bugs
6. Throw version 1 all together and release version 2
Perfect plan. Oh, I almost forgot, you're most likely to delete this post as it's "violating terms" ha ha ha.
 

First of all, I would like to express my great disappointment, I know that a great portion of people here may disagree with me.
Just imagine how it happened:
1. Release version 1
2. Users request tons of essential features, for me, mainly RTL support which is ESSENTIAL
"AWARD WINNING" software in "2022", and still no RTL support, I can't figure out how I paid for a software that can't type in Arabic lol
3. Release tons of updates with more bugs and glitches appearing every update
4. Fix bugs, new bugs appear
5. Development team is done with those bugs
6. Throw version 1 all together and release version 2
Perfect plan. Oh, I almost forgot, you're most likely to delete this post as it's "violating terms" ha ha ha.
 

If only the opposite scenario took place, I wonder how you would react then. Imagine if Affinity's software simply supported RTL by default but not LTR. I'm sure you will be the first person to whine about that.

Software itself in a nutshell.
Best regards!

Whether or not V2 is worth the price to pay again is a fair question for each person to answer for himself, and I don't mean to argue that point.
What I would like to point out, however, is that Affinity did not promise free updates on future versions. They have said all along that all of the V1 apps would have free updates, but eventually they would need to release new versions to continue funding development (and growing the company, as companies need to do). I wonder if people misunderstood the marketing vis-a-vis Adobe, where, instead of forever subscriptions, the apps (V1) was a 1-time purchase. And Serif really did support that for quite some time (between 8 to 3.25 years, depending on which app we are talking about).
 
No fear, you haven't violated the TOS for stating your opinion. Serif is a respectable company and welcomes your opinions, even the critical ones.

You got the exact point, developers can develop a "version 2" with "a lot of new features and redesigned UI" but can't figure how to develop Arabic support.

I may disagree with you regarding the cost..Development always deserves support..but I agree with you regarding support for the Arabic language, which is a primitive feature that many have requested for five years..and yet the slow developer who has been unable to solve the problem for years and years ignores it, even though it is a primitive feature.. I do not mind supporting the company and even bought the new package.. but I felt frustrated and even defrauded due to the lack of real development or a solution to a permanent problem for years.. I hope the company will provide us with a solution to this problem with the same seriousness that it cares about in sales and marketing.. Very frustrated. Instead of congratulating you on the new release, I feel that I have been scammed.. Please accept our opinions with open arms and try to solve the shameful problem.

Thank you so much everyone!

FWIW, it looks like from that site that the Bicubik font is a very close if not exact match.

FWIW, I came to the same conclusion!

The zip archive attached to the OP is accessible, but the ‘affinitycaff.com’ website is not:

I think BitzSec is chasing the file, not the website so that should be ok.

Thanks guys, just figured out that the file is actually attached

Okey, guess I'm gonna buy one then
Thanks everyone for your fast responses.

Okey, guess I'm gonna buy one then
Thanks everyone for your fast responses.

Okey, thank you for this, I contacted that email you gave me