Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

hawk

Members
  • Posts

    116
  • Joined

  • Last visited

Everything posted by hawk

  1. I know, I'm trying to insert e.g. page number which is not blank. Nothing happens, history doesn't change, highlight fields doesn't show anything.
  2. I do have a text frame with a blinking cursor in it, but still can't insert fields.
  3. The fields studio doesn't seem to respond to any clicks. Expanding/collapsing the categories works, but click/double-click/drag/right-click on field labels or values does nothing.
  4. 1. Creating a symbol from a layer containing existing symbols keeps the existing symbols linked to other instances outside of that layer. The problem is if you later want to detach the super-symbol, all of the contained symbols are also detached. I think the simple solution is to just detach the super-symbol / skip over children that are symbols themselves. 2. (See Attachment) What if I have a bunch of symbol instances in a pattern and want to duplicate the pattern and make alterations to the symbol instances while keeping the changes separate from the original pattern, i.e. duplicating the symbol & pattern together? I couldn't think of a good way to accomplish that.
  5. @hhauten did you click the hamburger menu in the top-right of the color studio?
  6. When I add a radial gradient to a live filter to mask it, sorta like a vignette, then do something else briefly, then decide I want the gradient to be a bit smaller, I have to change the type from None to Radial again, and the second color stop from light gray back to black, even tho I just used these settings a minute ago and didn't create any other gradients. It seems like it should remember the most recently used settings, at least within the same session. It's a problem with other tools as well for me.
  7. Yes, it still crashes in build 58. Specifically when switching between a facing and non-facing master page. @Pauls I tested 'OpenGL (Basic)' and Software. OpenGL was the default selection and Metal is disabled for me. It crashed and kernel-panicked in every case. Sometimes it freezes upon trying to create the second master page, with the master page settings window partially faded away. Sometimes it crashes the first time I try to switch between the masters and sometimes only after 3-5 times switching back and forth. No artboards, I just created a new document with default settings. It's not affecting any work for me by the way. I just happened to run into this while pocking around. Please enjoy your day. Newest crash log: Affinity Publisher Beta_2018-09-07-142515_Hawks-MBP.crash
  8. @woefi I tried to recreate your second pattern with power duplicate but there were several obstacles: I could not find a way to set a polar offset. After duplicating and rotating, typing a value for x position just moves it along global x axis and not local. Alignment handles can be dragged along angle of rotation, but it's totally imprecise. I'm not sure if any of the math expressions would be able to accomplish this. Sine function? I'm bad at math. Trying to work around this I created a temporary grid and constrained drag 5mm away. The problem is that this is not precise and the transform panel coordinates are still in the global coordinate system. Then I had the idea to duplicate & move the dot without rotating first, group them & rotate it, snap it so that the first duplicated dot was exactly on top of the original first dot. The duplicated second dot was then in the correct position, so I deleted the other dots, duplicated the original dot again, rotated it & snapped it to the second dot that was already in place. Now I could power duplicate to repeat the rotation & offset. Then I tried to group the first row of 39 dots and repeat the procedure, but the result was not as desired. At this point I give up in my personal challenge. It's a contrived example, so I don't know how much it really matters. I think a non-destructive transform effect would be nice to have though.
  9. Edit: Nevermind, I didn't read correctly. See @mac_heibu's answer. Edit --> Paste Without Format ⌥⇧⌘V Or use a clipboard manager like CopyLess to remove formatting automatically.
  10. I wish I could clear the kerning/leading shortcuts in preferences and the standard OS X behavior would take over.
  11. It would be more work up front, but I think they could create two generic software layers that would translate a Mac-specific protocol (Apple Events) and a Windows-specific protocol to an Affinity scripting API. Only the Affinity-facing side would then have to be updated in the future, with perhaps a little bit of extra work to expose the actual API objects on the platform-specific sides. Thanks.
  12. I think you misunderstood my point. During the early development of a software it is a dichotomy. You either try to develop every feature simultaneously (suicide) or you have a small list of features you develop, and add & remove items on that list. How you choose which items to add to that list depends, and obviously important features take priority. But obviously there's a period between the beginning of the development and some point in time during which not all important features are implemented, and my point is that we happen to find ourselves in that time. This is also a false dichotomy. And adding more cooks isn't always the answer. This is untrue and you know it. Serif obviously knows their audience and the competition, they're not morons. It's evident from the other two apps they've already created and how they communicate. You're just unhappy with the product in its current state, and are not acknowledging the actual phase of development we're in. "Alpha," "beta," "release," "v1.7" are arbitrary labels, and I've seen software at vastly different levels of quality from each other at each of these "stages". They're just organizational constructs that have nothing to do with the product itself. If we merely assume that Serif are competent, (and that's all we have to do), then we just have to look at the current state of the product (and our expectations of the finished product) to determine its progress in development. Don't get me wrong, there are definitely certain notions we associate with each label, and there's some theory about what they should mean, but in practice people have wildly different ideas what is alpha, beta, etc. A missing important feature could arguably mean alpha, beta or 1.0, depending how the developer sees it. In this specific case, Serif deemed it not necessary for 1.0 and although the reasons are perhaps not entirely known to us, I assume their goal for 1.0 is to have it usable for small projects like brochures, which it seems like it will be. At worst you can say that the choice of label is odd, and potentially damaging to Serif's reputation. But this is not a criticism of the product itself, or the competence of the development team as programmers, designers, etc, but rather their communication/marketing/business strategy. Maybe I am misunderstanding and that's what you mean all along... It's clear to me from their communications on this forum that they do not intend APub to be a viable replacement for everybody. But it may be for some, and it may be a nice entry level alternative for budding amateurs especially. Think long-term, think like a business person. You wanna reel them younglings in, and the sooner the better, so while they're still learning the app and becoming more ambitious, you're developing it further. Also, they won't have as many expectations going in, and every new update will feel all the more like an upgrade. In the end the goal is still to create a comprehensive product for everyone, but it makes sense from a business perspective (to me as a layperson anyway) to get in early. Keep in mind APub was already delayed. They just didn't want to wait any longer and it's understandable. Yeah, they just need to copy-paste 20 lines of code, right? The Affinity team has made it clear that they don't want to just take existing paradigms and add a little bit of polish. They're trying to understand how and why people actually use those features, and how to better serve those ends. This requires thinking a little bit outside the box, and carefully weighing a lot of options, and unless your friend knows exactly the variables involved, and the internal structure of Affinity, his opinion is not necessarily insightful. Even just a single detail can massively complicate the solution to what might seem like a simple programming problem on the surface. It's safe to say that Affinity is a little bit more complex than Notes, and sufficiently different from other apps that their solutions wouldn't necessarily transfer over easily. To sum it up, you're basically just dissatisfied with the current state of the app at the current point in time, which really just means that Serif, to you, is working too slowly, and I can kind of agree with you there. But we don't have all the details, and in the end quality is king, and if time is what Serif needs, then so be it. Pressuring them about things they already know isn't gonna make them work faster. They might re-prioritize this feature specifically now, but it would be a trade-off and somewhere in another thread someone like you would remain unhappy... The answer is patience. To finish I just want to quote @Dave Harris 's earlier post because it actually underlines several of my points so well: Btw, I'm sure your input here is appreciated and I appreciate your perspective too, but we clearly can't have all the things we want from APub at this time – that's non-negotiable – so let's try not to be to negative about it. It ain't gonna help.
  13. Firstly: A lot of drop-downs/popover GUIs sound an alert and flash the screen (as per the OS X accessibility option) when I press ESC. Examples: font size dropdown, text justification dropdown, . This is not the correct behavior, as this error normally means "invalid input". In this case I'm pressing the escape key to cancel and close the GUI element. Some GUIs don't do this, but instead cause my object selection to be cleared. Examples: stroke settings popover. Some GUIs correctly respond by closing without an error and without clearing my selection. Examples: font family & font face dropdowns, color selection popovers. The gradient settings panel specifically ignores ESC altogether. Please make the GUIs respond to keyboard input consistently! My second request is simple: the symbols sync on/off button is a global toggle. Please add it to the menus (under Edit) so I can bind a shortcut to it! Thanks!
  14. I'm not knowledgeable about it, but my understanding is that scriptable just means "implements Apple Events", and AppleScript is just a language that was specifically created for sending Apple Events, but any language can do it through a Scripting Bridge. This would be a third-party software that the user would install, but this would not be up to Serif to do. Affinity would only have to implement one interface/protocol. For example, there used to be a software called JavaScript OSA (Open Scripting Architecture), which I could use to write scripts in the AppleScript Editor, but in JavaScript, to automate any application that already supports AppleScript. That software has been superseded by Apple's own thing called "JavaScript for Automation" (or JXA for short), but it seems to use the same basic mechanisms (Apple Events). In theory there could be an OSA extension for Python, etc, but as far as I can tell no one has made one yet. It would be easier to just create another proprietary scripting system, but tying into native/preexisting infrastructure and ecosystem would probably be better for the user.
  15. I think the best way to implement it is as a Scripting Bridge: https://developer.apple.com/library/archive/documentation/AppleScript/Conceptual/AppleScriptX/Concepts/scripting_bridge.html#//apple_ref/doc/uid/TP40006467-SW1 That way it could be scripted with AppleScript and JavaScript: https://developer.telerik.com/featured/javascript-os-x-automation-example/ https://macosxautomation.com/applescript/features/scriptingbridge.html
  16. I think you're misunderstanding. Serif could have had this feature in by now, but then any of the other features like advanced paragraph & text frame options, tables, TOC and baseline grids would be missing, and you (or others) would be complaining just the same. Try to see the bigger picture. It's just not viable to try to implement every feature in parallel, instead of getting a few features implemented to a minimum level of functionality, and then moving onto other features and iterating. This way there are parts of the application that are actually usable and can be tested. We're simply at a point in the timeline of Affinity Publisher's development where not all features are implemented, but Serif is giving us a sneak peek and taking our feedback. That's all it is, a sneak peek. Obviously they know the importance of this feature and I'm personally also disappointed by its absence, it's just not implemented yet. Alternatively they could have waited another 2-5 years - would you have preferred that? It's a privilege to get early access and you should be mindful of that.
  17. For MacBooks without keypad: ⌘⇞ is FN+COMMAND+ARROW_UP ⌘⇟ is FN+COMMAND+ARROW_DOWN
  18. The ability to insert shapes into the text flow is great. Even Pages has it.
  19. It's the first option directly in the Text menu. Hotkey ⌘F It's also under View --> Studio --> Find And Replace.
  20. Steps to reproduce: Create new document with default settings (non-facing pages). Create a new master page. Change document settings to enable facing pages. Create a new master page. Double-click the two master pages back and forth a few times. The first time I did this I actually got a kernel panic. My computer immediately shut down and restarted. It's rare that this happens to me so it was very surprising and exciting! Luckily I didn't lose anything important. Crash logs attached and also in raw text form linked below: Raw text: Kernel_2018-09-01-064628_Hawks-MBP.panic Raw text: Affinity Publisher Beta_2018-09-01-065022_Hawks-MBP.crash Attachment: Kernel_2018-09-01-064628_Hawks-MBP.panic Attachment: Affinity Publisher Beta_2018-09-01-065022_Hawks-MBP.crash
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.