Jump to content
You must now use your email address to sign in [click for more info] ×

Seneca

Members
 View Profile  See their activity

  • Posts

    1,325

  • Joined

  • Last visited

 Content Type 

Everything posted by Seneca

  1. Seneca
    Yes it is. Just change Walt's Replace: \1 with Replace: "\1"
  2. Seneca
    Don't you think that your sentence above is slightly insulting. First of all, the Global Layers are being worked on. There was quite a long discussion between the Affinity team and this forum regarding how this feature is expected to work. You shouldn't find it difficult to search for that here in the forum. Second of all, the 2.0 release is by no means done. The team is about to release version 2.1 with a host of new features and additional features will find their way into 2.2, 2.3 etc. So, while I understand the disappointment that the Global Lagers didn't make it into 2.0, this is not the end of the road for version 2. I'm not trying to defend Affinity here, I too would love to see Global Layers now but to say that they don't understand the importance of this is quite a stretch.
  3. Seneca
    I'm not sure what you have been reading but the pictures you have provided above clearly show the bleed. Everything beyond the crop marks is a bleed and your pictures clearly illustrate that. Am I missing something?
  4. Seneca
    It would be great if the misalignment fix in the Text Styles panel, reported some time back, made its way to 2.1 (not a deal breaker, though).
  5. Seneca
    For simple scenarios plain text rules. There are other ways of working with text in Publisher/inDesign that does not involve constant reformatting of the text. Imagine you share chunks of text among various publications using different templates and styles. You have carefully formatted your text in Publisher, applied styles to it and saved it for further use later. You also made sure that you name Paragraph/Character appropriately so that they are the same among various publications (in view of sharing). Sharing this text among publications in inDesign is easy because what unites them is the same paragraph/character style name. Copy and paste portions of that text and voila, done. The copied text adopts the look of the paragraph/character style of the publication you copy your text to. That saves a lot of time. Publisher instead applies strict rules to the copied text as explained by @walt.farrellearlier creating another style name to the publication, say Heading 1. To me flexibility exemplified by inDesign trumps Publisher's rigidity any time in my books. I hope one day we get some sort of preference switch where you could choose strict rule or name based rule when coping formatted text, and I can finally move 90% of my work to Publisher.
  6. Seneca
    I am also a long time inDesign user since the first inDesign beta release in fact. InDesign works the same way, so if you want to insert an inline picture to an empty paragraph, that paragraph needs to have the leading set to Auto, otherwise the text will not move to accommodate the height of the picture.
  7. Seneca
    Hello @Cogent30, Yes, this is a problem for me too. A number of users have already noticed that and have reported it as an issue but until this is looked at by the Affinity team you need to accept the fact that this is how Publisher works. The only way to clean up styles at the moment is to use Find & Replace and then select Paragraph Style/Character Style in Find/Replace options. For simple text processing this sort of dealing with styles is acceptable but as soon as your document needs to import/paste text from different sources with same style names this becomes a problem.
  8. Seneca
    It's difficult to judge but my initial thought is to check your paragraph styles. Your leading should be set to automatic, (the paragraph you are pasting the table into) because otherwise the table will not fit into your defined fixed leading, e.g 14pt.
  9. Seneca
    Hello @v_kyr, You are getting slightly unreasonable here. The team has stated, in numerous posts, that because the APIs are going to be the same for both C and JavaScript that they will keep the documentation in one place. There will be a lot of people for whom JavaScript will be the most important part and they will not regard this as garbage. They will concentrate on the JavaScript part and you can concentrate on the C based APIs. And they lived happily ever after. 🙂
  10. Seneca
    A regular expression, whether well-formed or malformed should not bring the program down. So I would submit this as a possible bug for the development team to look at.
  11. Seneca
    Hello @johndmoulton, Have you unticked the "Include on Export" option in the Section Manager Dialog by any chance?
  12. Seneca
    To get rid of the background in a text box just click the Revert Defaults button or Edit->Defaults->Revert. To apply a colour to the text background one would need to go through Publisher, which is awkward. I completely agree with you that it should be possible to do it from within the Designer as well.
  13. Seneca
    Make sure you have a Text Frame panel open. If not you can open in from Window->Text->Text Frame. Then you can change the background colour of the text frame or remove it entirely in the General subdivision which is at the tip of the panel.
  14. Seneca
    Hello @af-user, this looks to be Windows specific. I am on a Mac. I've just created a sample doc with a table placed on a master page and I can create pages based on that master page and edit the contents of the table without any problem.
  15. Seneca
    Yes it is. Just remember to use styles for your projects. If you applied a style for a Heading and a List of Contributors, for example, then just include those styles in the TOC Panel (tick them) and your subheadings will appear in your TOC.
  16. Seneca
    I would respectfully suggest to read (again) page 17 of this thread before jumping into any conclusions.
  17. Seneca
    I asked for a similar question earlier. Here's the answer given by TonyB: We will support a very limited set of platform specific automation functions with one of those exposed functions being able to pass a Javascript snippet that will then have full access to Affinity. Hope that makes sense.
  18. Seneca
    Opening up the API to different language through WASM would definitely be very interesting indeed. 🙂 EDIT: On the other hand the C based APIs will allow other language to plug into that and it doesn't have to be through WASM.
  19. Seneca
    Hello @CM0, I know this question is for Tim to answer, but my 2-cents are that we don't really need Wasm, since we will have C-based APIs. If we didn't have that, Wasm would be something worth considering. Also, as Tim says, the JavaScript performance is so good that, to have another layer based on Wasm would unnecessarily bloat the app.
  20. Seneca
    This is great. We all know how quickly this JS landscape is shifting under our feet. First we've had Node, then Deno and now a new kid on the block Bun, written in Zig language, extremely fast. Having quickly read some of the code samples shown in the video my conclusion is as follows (I may be completely wrong here, of course): 1. We will have a Macro Recording facility - brilliant. 2. We will have Scripting Facility - brilliant. 3. Not shown and mentioned elsewhere, we will have a C based APIs - brilliant. One thing I'm not clear about is whether we will be able to write our scripts in TypeScript as well as in JavaScript. In theory this should be no problem as TypeScript is a superset of JavaScript. To be able to give scripts a .ts extension and run it as well .js files would be a big bonus in my humble opinion. Basically what I am hoping for is to have an environment that would transpile TS to JS automatically. For larger scripts and for those who want to go the TypeScript way this would be really great. I'm sure the team at Affinity has all this covered.
  21. Seneca
    This is a very valid point.
  22. Seneca
    Hello @kimtorch, Tim and Patrick went to great lengths to stress the fact that this is just a very early pre-pre-pre-alpha, of what they are working on. This is not representative of what we get when this is released. And secondly, as far as I remember the team is also working on a C based extension system. For companies that need greater automation this plug-in system might be more suitable.
  23. Seneca
    You are right. I take it back.
  24. Seneca
    What are those issues and glitches you would like to pay double to be fixed. The fact the the program rightfully warns you that you are about to do something you might regret later?
  25. Seneca
    This has been requested by the users quite a number of times. This may be added in a future update, however, only Affinity can authoritatively speak about these matters.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

 Accept Cookies  Reject Cookies