narrationsd

Ok, here in the morning is a better version of replying with the proofs you asked. Late last night had been a little frustrating This is the box score, also notes, and with luck, the videos in proper order afterwards. I can't actually seem to duplicate the 'random' resetting of brush controller to None, if I am quite confident it happened, and multiple times. Perhaps I don't remember the triggering other actions before coming back to the brush and seeing this (or maybe I wasn't actually on the latest beta?). Selecting other tools, fooling with visible other settings, no luck. But there is something... However, I can 100% duplicate another case of the brush controller resetting to None. It happens after closing and re-opening the drawing. One would expect the controller setting to be saved with the document, but it isn't. For this, I made the requested film: controller-back-to-none.mp4, attached. Concluding with the more complicated item, I could certainly duplicate the troubles with multiple conflicting and improper settings of brush size, filmed in three-conflicting-brush-size-settings.mp4, attached, and with description(s) I'll put next. Here are the steps in the film for the multiple conflicting settings: I first set a large sized by the Toolbar Width slider, then drew with it: fat. Then I opened More on the Toolbar, and slightly changed the Size Variance. This caused the brush to go to the More window's Width setting. I drew with it: thin. Finally I moved the Width slider on the Stroke panel -- which should have absolutely no affect on a Brush...and found the brush following it, to extent of its range. I left it at medium and drew; got medium width on the brush. And here are some things to note about the conflicts: The width from the stroke panel and the Toolbar track, sort of, but don't at all match: 186.6 toolbar vs 41.1 on stroke (anyway, this should go away). All three of the width inputs interact, improperly. Clearly strokewidth shouldn't affect a brush. If Toolbar and More width are going to interact, the current Toolbar setting should be pulled into the More panel when it opens. Then it will also always be possible to set it differently there if you also want to change the width. Ok, a little editing for clarity, and now I try to add the movies at the end. controller-back-to-none.mp4 three-conflicting-brush-size-settings.mp4

Something changed in the last updater so that the desktop beta icons shifted unpleasantly around. Although I had the icons positioned to taste, they ended up being put first in icon ordering after the trash bin, thus altering the order in which I'd had everything for familiarity. One would guess that the change is that the old desktop icons were deleted, instead of being over-written. I'd agree having them produced should be optional in the install sequence, but please revert to where you simply over-write instead of first destroying. Thanks.

Pressure sensitivity enabled on a vector paintbrush makes a mess if you hold or stop at either end of a stroke. The smoother paints on the attached screenshot only appear from smooth brush movement. Trying some dots will give you the best way to see the problem -- as the very ragged/jagged dots on the pic. Or just stop a brush movement as or before you lift it. Either way, you can watch Design try to build a cap, and fail to do it nicely, as it also has on the ragged-ended lines where I stopped the brush or held it at starting. Turning off pressure sensitivity gives nice round caps. I had about 80% width control set on the pressure controller. The controller for vector paint brush is always reset to 'off'. Seems it should hold your current setting between tool selections -- and also when re-opening a drawing. The same stability/memory is needed for the size of the brush: setting several other things will revert it to 16px size. There are funny interactions (changed brush size, etc.) if you open the end caps tab and try to make adjustments -- only brush should work with brushed strokes. And if you set to brush, it doesn't change to a brush from a line tool, also. Apologies for the stark look of the screenshot -- I took out opacity sensitivity to assure the simplest example, and same reason didn’t work in pleasant colors. All the results are with the very latest Wacom driver, and my Intuos 4 tablet. 1.7 gives much the same results, while Illustrator CS6 gives nice and smooth variable strokes with the same level of pressure sensitivity.

...changed the title to the fresh version I was actually testing. As well, noted one more reason to have an action for mass-changing quote styles. In my testing, I'd manually rewritten each quote with automatic typographic preference set, which is what you tediously have to do now. And then when looking again, see I'd already missed one. This is bound to happen, without automation to be sure all are covered. And it also points up that the spelling error occurs when only one of the quotes is not the typographic curly sort... Thanks again for attention on these things, Clive

Walt, thanks for your thoughts. I tried typographic quotes, and indeed spell-check does recognise ordinary words correctly if those are used. We still do need it to work properly with ordinary single or double quotes...typographic are often not used for reason, if sometimes also used. However, there doesn't seem any way to automatically change to typographic quotes. I had to manually edit, with the typopgraphic auto-correct turned on. I think this has been raised before, but there really should be a feature to mass-edit a document and change quote styles. This is particularly needed for any imported text, or text from an editorial app like ProWritingAid. So I hope it is on a (soon) feature-to-be-implimented list! As I think you note, this method doesn't help with hyphenated name spell checking. I think this is a must feature itself. We have such names just in English or other cultures, and as importantly, perhaps even more so, need to spell-check transliterated Asian etc. names. All of these have hyphens. I Recognizing hyphenated names etc. would add a slight complication only to a spell checker: that it recognize part-of-hyphenated words themselves, or over-ride when the entire hyphenated group is a match. I think that covers it, and hope I am reporting in the correct place to get necessary features added to Publisher. Which is shaping up to be very useful indeed -- I keep InDesign CS6 still, with good practice, but it's not going to get any security updates, etc., so as with Design and Photo, I'm very happy to have purchased the Affinity tools. And not least for how well they work, often with a lot of cleverness that works, compared to their predecessors. Appreciated, Clive 

Nice to have the new Beta, and I noticed the Preflight had gotten smarter. However, there are a few problems which you can see in the screenshot: 'meet' is flagged as wrong spelling, apparently because it's surrounded by single quotes trickier: O-Ryong is a name (Korean transliterated). I could allow Ryong, but really I'd like to spell-check O-Ryong. Can you provide a way? Asian names not being uncommon in our globality... 'Have is flagged as wrong spelling, apparently because it's preceded by a single quote, as part of a longer string The Non-proportional Scaling flags I'll have to look at -- I didn't think the pix in the doc were, but could be you caught something. Or, it's to do with how I adjusted them in, via Design...we'll see

@Jon P -- well, I wouldn't let the developers off the hook so fast, with a respectful nod to all the things they do accomplish very well -- for example, the way image functions are so much better than 'the other brand'. I think the problem Joachim raises clearly is behind the difficulties I had exactly with replacing images, in fact when providing files to test another bug. These were _quite_ frustrating, as nothing worked at all as in InDesign, which uses frames galore, but is sensible about them. I finally ended up fresh-creating images, as seeming the only sensible way after enough time wasted. But this should never be. I'll suggest a simpler way yours can work, which will also not interrupt anyone who might be used to another. I would feel: clicking on an image and replacing should...simply replace the image. What else wouild be sensible?? If 'frames are always present', fine. Replace the image, as you know what's inside its frame. The name of the frame should say that it is one, as opposed to being the image itself If you click on the image inside the frame, once again replacing should replace it. This kind of situation arises when 'programming thinking' is held above user thinking. If you want to use a particular kind of structuring internally, fine, please do butalways, make the use presentation simple and direct. No extra hierarchies should interrupt, as at present here. Best to each, Clive

Ok, that makes sense, for placing items off-page, and I just checked that it works on the bottom also -- yes, it does. My original point was the reverse -- I couldn't scroll to see more than half of the last page. Again, though, I haven't seen that repeat, and it could as always have been some display driver etc. issue, though the laptop is very up-to-date, and doesn't otherwise show things like this. I'll keep an eye out, but we can consider this closed unless seen again, seems wise.

In truth, I'm wondering about it, as haven't seen this again for a while, and also note that you can _always_ scroll into a blank area above the first page. Do you guys intend that for some reason? I'll keep watching, exercise endpoint scrolls when I think about it. Thanks, Jon.

To frame, I don't know if this is related to Losing Scroll-ability or might be an always possible artifact of a graphics driver, but this time I have pictures, and you can try for yourselves. Have a pair of linked pages, with orphans/widows/para together set, and two paragraphs on either side of the resulting automatic page break. With two sentences in the second-page paragraph, all arranged as in the before-edit.png attached. Now split the second-page paragraph, by typing a return between the two sentences. Then you have lost the first sentence, though there's a clue to where it is because I haven't yet added the formulation of 'Ok' as allowable spelling. See this in line-gone.png attached. Finally, click in the initial page. Pop -- the sentence shows correctly. As in click-and-back.png As far as many other applications show, I don't seem to have a problem with my display driver. To get this fault sequence to play properly, you'll probably have to adjust until you get the text vs. text block boundary appropriate so there's room for the one line, but not the two-llne paragraph on the first page. This is easily done by moving the bottom of the block. Cheers on your own holidays --- I was working on instructions for a gift, which with Publisher came out nicely... p.s. image handling in this forum seems a bit impossible. I put these in order here and with introductory lines here, since the forum wouldn't let me control order, nor did it print names/captions. But still there's another copy of each, lurking out-of-order, beneath these initially. And I can't even control spacing. So don't get confused - it's all in these three screen captures... 1. Initial state image: before-edit.png 2. After splitting second-page para with a return, mostly invisible sentence: line-gone.png 3. After clicking on first page, sentence appears there: click-and-back.png Everything below here is just duplication by the forum software, of the three in-line inserted images... more text just to split... more text just to split... more text just to split... 

Really enjoying the Affinity set, composing Christmas letters with illustrations, using Beta Publisher, Design, Photo to so easily make images just what you want, correct tilted scans and appropriately mask them, etc.. The 'newsletter' resulting is great each time. So, thank you very much for the work you put into this whole package, and how it works. Truly appreciated, and since Apple once 'invented' Publish-Subscribe as one of the many early attempts at this. Yours...works! Now, this bug is something I noticed a while back, and just ran into again on these letters. I''d been working a while, and suddenly the page view offset itself from scroll control. the viewed pages slid down a little more than half a page thus you had a grey void at the top and couldn't scroll to see the bottom of the last page neither trackpad or window thumb scrolling would work I tried a number of things to shock it back to sensible; none worked exiting Publisher and restarting, the file was fine, and proper scrolling on was recovered I am really sorry not to be able to tell you what set this off. It's happened before on a much shorter session. And, I didn't get a screenshot either. But you can readily imagine, I suspect. Best in the holiday season, and remembering some consulting years and travels, in Northern England, Clive  

Nice to be able to report that on Beta 523 this item is essentially fixed. By the time the afpubis fully loaded, the linked image now shows in full. It is still a little hinky-- during loading phase, the linked image is still showing only a quarter. Would note that resaving didn't seem to help with this, and that it's more evident on a longer document than the demo, so that it takes longer to complete loading. You can show this solidly by just adding pages onto the demo. The one I'm looking at has about thirty pages, almost all text. You'll likely want to fix in full, but should be just a matter of ordering and/or when to event/publish to actual display... This will make overall impression as comfortable as it is now once document fully shows. Cheers to devs

Jon, sounds good - that's just what you should see. The rest of the information is to cover results of variations, which may help home in on what's actually going on. Glad to hear you guys are on it -- quite appreciating both what Affinity does, and how each of the portions continue to improve.

Hallo Joachim, Interesting idea, but there isn't a path in the PSD -- just had another look to see, using Photoshop CS6. I'm hoping the stark appearance of the image, precisely one-quarter visible, should alert the developers to the problem they apparently solved before Beta 518, which will make it easier to understand what's still triggering it. Interesting name for your village... Grüss, Clive

Jon, apologies for the delay -- had to wait for the weekend to spend the several hours it took to narrow this down, and produce demo files that should let you play with it. Along the way notes: this problem occurs on an afpub that was generated from an Indesign idml. theidml was a bit of a mess. I cleaned up the area of this image, but problem remained. Actually creating an afpub with the 518 beta and this image, there was not a problem - was clean Then, here are the particulars for the demo sent, same on the original As you receive it, even the thumb image in the Windows 10 latest everything file preview is quartered the same when you open it If you save a copy of the afpub, and then change the image to Embedded, via the Resource Manager, save, close Publisher, and reopen, the problem will have gone away. If you save another copy, then with the Resource Manager Replace the image with the nearly identical brignt.psd provided, save, close Publisher, and reopen, the problem will go away(!) The trick of it is, the original afpub has the linked image _named_ the same as was in the idml and preceding imdd. However, I created this by opening the original image with Affinity Photo, clearing the content, then pasting in the same image as in bright.psd, adjusting so it overlapped the boundaries so those remain the same, then saving under a name that's 'near' the original in the idml and afpub files. Just -b added to the name. once you've cleared the problem by embedding the File0773soft25b -b.psd, it will not recur. You can Replace the embedded with the same file linked, and there will not be the quartering problem. I'm a little surprised this didn't turn out to have to do with the exact file name. But it may well have something to do with the exact dimensions of the psd, which is why I created it in the way I did. The original jpg for the psd-- if I linked that, no problem. Problem only on the psd. I'm not giving you that original jpg as it's private. But you could perhaps duplicate this aspect by exporting the psd to a 100% jpg. I would guess that is not going to have the problem either, when you link it. Bu then in my experience going back to linking the psd will. Ok. As you may imagine, there were lots of intermediate steps to arrive at what could duplicate, and in a small file. I nearly gave up, but persistence got you this demo. I hope it helps clear up a corner in Publisher -- seeming likely to have something to do with creating an afpub out of an idml, but maybe it's just something about that psd and the framing dimensions. And, just before leaving this note, I had a look inside the demo file, and found a bit left over of the original mess -- all the groups around the image. So, I cleaned those out, and in fact removed the extra Layer, so that there is no grouping, just the image and a blank caption (which lies in its 'from jpg' name). The quartering problem still remains, so has not to do with any extra layering. I wish you guys fun, and actually hope this winnowing, demo, and counter-demo procedures will leave the cause clear. Regards, Clive files are in that Dropbox bucket you provided  

I opened a project which had been fine in last beta, and found a main image was showing only 25% of its content, per attached pub-on-open.png. Experimenting, I found that magnifying the view a few times in succession would bring back proper 100% display, per attached pub-after-several-resizes.png Saving the project with 518, closing Publisher, and reopening on the project didn't help -- same 25% result showing. Life is sometimes a mystery, isn't it...!

Jyscal, quite glad you got something that works for you. Why it's better...well, software on Windows, as mentioned. And/or maybe Affinity had improved their fonts-with-issues handling. Points, and reward, for keeping trying Take care, Clive

Just spotted your reply, Jyscal... Well, 'KNOW'ing things are ok on any Windows machine isn't all that easily reckoned, so patience is probably in order. I was looking above to see who else might have offered tips, and wonder if you've tried as @Callum from Affinity suggested, _removing_ those extra fonts you recently added, all of them? You might well be surprised at the result...or yes, not. Also, you might look at the size of the user community, and realize your experience isn't what very many are seeing, which is a way of knowing matters can be more positive. Now, these Affinity apps have at times been slow on font loading when in much earlier betas, but I just cold-started the latest released Design, with hundreds of fonts, and it was up in about 20 seconds. This is on a reasonably fast laptop, probably most importantly to say having an SSD. InDesign, a comparable program to Publish and this set in general, took a little over half that. But also...here's a substantiation for the way I'm telling you this story... Actually, both these times, especially InDesign's which was much slower, are definitely faster than I have been experiencing, for some interval. And what is different is that I had a big upset on the machine last week, due to a bogus Microsoft update of Windows, and in concert with some very sharp depth-level support people you can actually reach there (in India...!) , with enough persistence in such cases, in essence the entire Windows 10 operating system got cleared and reinstalled, along with a number of necessary adjustments. Yes, this can be done, and it's better than what they used to tell you, which was just to start from scratch and rebuild the machine in toto. The new way, your apps and files stay undisturbed...and actually did, including some with dire copy protection. I am not suggesting you do such a thing, please be confident. I am just noting that on my own would have to admit somewhat expertly maintained machine, which I had felt was as clean as experience could say, it obviously wasn't, just in the ways we are aware Windows always has been able to fall apart, invisibly, crumbling from within. What I would do, is try the step of taking out all those new fonts. If that doesn't clear the problem adequately, the font manager solution I proposed will allow you to slim down to just what you need, which should get you through, and may even help see where there may be a corrupt font install. Those are very, very well known to be able to clobber any particular software -- and yes, not necessarily _every_ software. If you find the bad one, you could even send it to Affinity, so they could add some additional bullet-proofing for its problems. Hoping this with above will help you, and anyone else who hits such a frustration... Clive

Hmm, sounds something is really wrong here. You mean you see the problems without opening some gargantuan document, will suppose -- and second open should be if anything faster than the first, as Windows caches at least portions of apps. I have a lot of fonts, probably, and Designer takes just over 400_M_B, Publisher 800 on the fat magazine demo which also has a lot of large images. It wouldn't hurt matters if you afforded 16MB as more reasonable memory these days, especially if you want to run several programs like Affinity's efficiently, and there's always a lot of responsiveness to be gained by going to an SSD from the usual hard disk, but you shouldn't be seeing what you are without these. I'm not going to be able to contribute more this time, but here's Microsoft's instruction page for ways to start your laptop in what they call Safe Mode. MS Safe Mode Safe Mode will let you see what happens without all the add-on invisible programs we end up with, running in the background and sometimes interfering in significant ways with programs that are well designed on their own. If Affinity runs nicely in Safe Mode, then you can look into taking out extra background apps -- there are lots of instructions for going about this on the web, perhaps easy to find if you also mention Safe Boot. The efficient way is often referred to as bisecting, or binary search, meaning you take out a noted half of those apps, then see; if no change, take half of the remaining half; or if change, put back in half of what you took out, etc.. Many of the background apps can be disabled from your Task Manager's Startup tab -- easiest to start with these. Others are Services, which you can look up how to disable also, for a rapid test before deciding to de-install anything. I guess it should be said that another way you could be having problems is if you've caught a virus or trojan; I tend to think of having excellent protection and habits always, but these can slip through and use your machine for all sorts of things. Norton Security is for many years very efficient and very good, and they also have a power cleaner if you find yourself deep in problems. Depending on skills etc., that's the sort of thing where a trusted local service could turn out to be useful. Hadn't intended on covering a gamut, but there we are...

@Jyscal, answer is possibly get and use a font manager. - this way you don't have to hve all fonts loaded all the time - you can arrange them in (overlapping if you like) groups, according to task - you can list favorites - more complete ones have analyzers for duplicates and font problems, which will help aoid slowness and possible app crashes Which are good? Well, I haven't really favored most; they tend to stall in contemporary development, or be awkward. The one I liked best, NexusFont , was nicely presented, but the developer moved on. There are the expensive ones...most of the rest have free not-very-limited tryouts so you can see. The one with an endless-draining subscription has, of course, a gaming-you very limited tryout. - MainType may have some balance of awkwardness and features; it will ding you for paying every time; the trick to shortcut its button-hopper is to say you'll pay, then cancel, until you do choose to - Typograf might be worth a look, if it's quite opinionated - if an office pays, one of the higher priced might be worth their hundred Euros - the best I expect is to ask your better printer or layout/design pals, see what they prefer... good fortune - be the foxy hunter (since this forum knew there was an emoji -- and curtly refused it)

Well, just to say, I did install Inkscape on Win10, and try it...on a photo, was just trouble. I am sure those who put the effort in long ago to figure how to treat it for getting traces still can, but... An opportunity we'll hope Affinity finds their moment to pick up on, here, and I guess they know that.

Translation (rough, but you get the idea...) Axel Foley, una sugerencia. Puede usar el Traductor de Google (translate.google.com) para sus publicaciones y para recibir respuestas. Está lejos de ser perfecto, pero utilizable, y creo que el idioma español no es una habilidad amplia en Nottingham, Inglaterra, donde se hace el software.

Yes, and as Potrace is not available in any of its Gui forms _except_ on Mac... However, I had a quick look this morning, and: - DrawPlus, you'd need to buy, to try - Microsoft's ancient Expression is listed and downloadable, but the tracing is dire - So I fired up my CS6 end-of-life Illustrator, and contrary to memory, its trace seemed quite good. It's maybe the presets, kind of hidden on the invisi-bar just above the drawing, which is making this so. - Thus, as long as tracing images which are your own or from sources you know you can trust, Illustrator if you have it seems to enjoy a long coming life. - And Affinity deals nicely with Illustrator files, so there's no loss of effort there. - You'd still think the bright in Nottingham would do a nice job of tracing without too much taxing of themselves, but just possibly there are more pressing matters...we should understand

Have to say, watching that tutorial shows DrawPlus's tool to be very nice in operation. For $25/UKP20, it seems a no-brainer if you have the need, since Affinity / Amazon still allow purchasing the no-longer-supported final version. I'm not expert on these matters, but as far as trace quality/ies, there are a lot of comments in this thread saying (artistically) pen-tracing often beats auto-trace. This would fit my experience with Illustrator -- by the time you play with settings enough to get near what you want, the drawing board grows in atraction to tastebuds. Maybe that's a point of view that could draw Affinity designers into a different corner...they do such good work in producing tools superior, not just replacement, for Adobe's, and here there's the opportunity to make 'appropriate technology' out of the DrawPlus bones. By which means, easy appiication, of course in new Affinity apps style, abilities attuned to producing the level of result really useful autotrace can, while leaving the unattainable 'touch' to manual tracing. The software could even say so...

That was a stunning set of demonstrations in your release Event. And it's a great accomplishment, how far you've brought Affinity/Serif, not to say a bright future. It pleases me greatly to see this come out of the Northern England where I once had considerable experience consulting to then-software companies. Studio Link is marvelous - because of your architecture. It really is instant, with no need to have the subsidiary applications open. This is truly well done. Of course, I couldn't run it. Not until an hour of troubleshooting, as there was no link up yet with suggestions. I will make another. First, i have to say that I contacted you on the Beta forum, to 'suggest' with greybeard experience that you just possibly might want to actually Beta this, before today's big bang. This was summarily dismissed: 'we've done a lot of testing you haven't seen, and you'll be surprised.' Just like the Lancashire Girl, who famously 'can't be told.' Of course, this is Marketing driving the ship, and it really shows. And could be a learning moment? Ok, here's what this cost me, perhaps with too much knowledge aforehand, and of course not the detail you could never know. have latest betas of all three installed, long Beta participant upgraded to latest non-Beta Designer and Photo, last night download and installed the Publisher release. Strangely, I don't believe it asked me for a key, but maybe. looks to work, as expected, so let's use the Design personality. Fail. Get alert below, which one would get very tired of, saying I hadn't installed. de-install Design and Photo. Reinstall. Validate keys. 'Open' as required. Fail Studio Link, 'not installed' again. de-install all three. Reinstall. Keys asked for Design and Photo only. Runs. Fails Studio Link again. try to get smart. Believe it might be because I run Win10 (very latest 1903) always not-admin for security, as sense must. So I change login to an admin one, re-login, delete and install all three. Fail. ok, getting serious, and a serious waste of time. I continue as admin, deinstall all three, hunt down and find the Program Data Affinity folder. Delete that, and this time didn't have to delete a Program Files/Affinity folder, as somehow this deinstall properly zapped it, which others before did not. Probably to do with that non-admin running installer and permitting by another admin login's password., no? install all three, try them individually. All three now do require a key. Shut them down, all. run Publisher. Try Studio Link. It works. Fantastic. An hour gone. But it is extraordinary, one more great tool from you guys. _then_ I look again, and there is finally a post. About ten down in it, someone from Affinity finally stops asking 'if you installed', and comes up with a very targeted removal which I presume does answer the issue. -probably this file-to-be-deleted (again requiring admin permission, and lack of fearfulness in monkeying with Windows' innards, a fear that would be fully justiied) is surgically targeted this way to avoid taking out recording of license keys, etc.. But. Now, you have to ask: a. why on earth not have the Publisher installer take out this marvelous blocking file with the long path?? b. we can answer, probably: you didn't know. c. now we are back to Marketing-directed refusal to Beta, so as to believe they will generate the Big Bang d. and/or, the person who answered me with such cussedness is like a fellow who really was the guru in one of those Northern concerns twenty years ago, who I liked, but would respond straight to customers with his famous intonement, 'Works as Designed', if any treaded on weird and wonderful 'features' that had done them in -- if he felt that was right and had a reason, yes. But a little open hearing would have told him more. You guys are doing wonderful things, and I have told many of those I've found, the ways your tools are very much cleverer in thinking that makes tough image needs easy to solve. I hope you will take some lessons, and not spoil it again by some move that flies in the face of sense any actual maker knows, and for some reason all tied up in wanting to puff up. You don't need gimmicks to have the right to feel puffed up. That's what I'd say... Regards truly, Clive not a Brit, but I lived a long time there once, and I quite remember a fine-ness in my time...