bpedit

Thanks. I was aware of that feature in Export, you're correct that it seems to remember the setting (until closed anyway). My question was directed at trying to avoid the Export menu and just saving directly. But on further investigation it appears that, at least, the name is preserved as the default save name in Export. So this means three extra button pushes and two extra mouse moves per image compared to a simple save. Times 3,600 images! Walt: I understand there's no inherent metadata of the saved quality, I was hoping for a way to set a default quality applicable to the Save function. Poor titling on my part, sorry.

I have massive numbers of digitized slides to process. I'd like to open each, make a few adjustments, then save as a JPEG. But when I do the file size bloats tremendously from, say, 1.3 Mb to 6 Mb. I suspect this is due to saving at 100% quality. If I export the file instead at, say, 95% quality I get a reasonable file size. But what a hassle invoking Export, changing the quality (I think it then remembers this) then entering a file name and saving. Is there any way to set the default quality as applied to simply using the Save button on an open JPEG?

Better yet, how about a choice, upon being notified of the conflict, of deleting the conflict without having to navigate to it.

On further testing, I see a bit more detail on this issue. The Placed image, when subjected to a paint operation is "rasterized". This was happening automatically by "the assistant". If I disable this assistant and rasterize manually, I get the same result. If I change the document resolution to a much higher DPI, the original image quality remains after rasterization. But when I reduce the DPI back to 96, the image resolution is degraded accordingly. So I'm guessing this a limitation restricting images, except those freshly placed without having been manipulated, to the document DPI. I understand how this should be so in the Photo app but is an inconvenience in Designer, at least for me. It's ironic that I must use the 96 DPI for vector output, not because of any raster content but to make the size correct for use in creating gcode for CNC!

I'm importing high resolution images into Designer for using as templates. When first imported the image looks fine. But as soon as I use the Erase tool to cull portions the resolution is automatically reduced. I suspect this new resolution is that of the document which is 96 DPI. I must use this resolution to have my exported SVG's sized properly for CNC work. But my final output is scalable vectors at far higher than 96 DPI. Is my supposition correct or is this a bug? If not deemed a bug how do I override and maintain full resolution? As a side note, this seems like aberrant behavior either way. If the image is degraded to a lower resolution at the onset of the first manipulation it seems that if moved a non-integral displacement, interpolations will occur that will further degrade the image. What not leave the information intact until output time?

Yes, I wondered about this being an iOS thing too but concluded the look of the window and the prompts suggest this is endemic to Affinity.

Not the same as what most of us construe as "saved". Saved, in a functional way, means you can access it on demand even if you have closed the current file in Designer. Saved also means it was in a particular state when saved, not the current state of the working file.

This applies to using 'Saving as' to make a new copy from an existing file. After entering a new name and the 'Save' button is hit, the screen opens where you can select the destination. At the top center this reads "Item will be moved to "[filename]" on. . .". The button in the upper right, as well as the title just referred to, should read Save[ed] instead of Move. Otherwise you would expect the new file to actually exist if you don't click Move which is not true. I'm not sure what the conditions were but on one or two occasions this button did say Save but I can't get that to repeat.

Get rid of the Stroke Width slider, along the screen's left, when in Point mode. This is taking up valuable real estate, we all know where to find it the few times (never for me) one may want to use it editing points.

In the Export window, at least in the SVG format, 'Use document resolution' is ignored. My standard resolution is 96 DPI, necessary for SVG sizing of code on CNC machines. If I overwrite 300 in the DPI slider with 96, all is well. But when choosing the 'Use document resolution' toggle I get something different. This is not new to v.2, it was extant in the previous version. BTW, in the DPI slider, how about remembering the last used resolution instead of continually defaulting to 300. I must change this 30 time a day being painstakingly careful each time.

The "measurement tool" is a big tease. It seems like it's most of the way toward a far more useful dimensioning ability, one that remains in place.

Please add a hundredths place to the displayed value for line width on iPad. This could be optionally toggled on/off in preferences so folks not needing it view a less cluttered display. Most of my work with Designer is generating SVGs for CNC inlay work focusing on engraving. I work in millimeters and the fattest line width I typically use is 0.15 mm but often use lines down to 0.02 mm. While none of this matters to the final SVG output this precision is instrumental to layout spacing and design. edit: Please also apply this to the Transform display.

Why does one have to choose? I want the trash can too! Much better than keeping the Layers palette open and constantly darting over there for deleting. My current project requires massive amounts of deletions resulting from the Divide operation. But thanks for the response. edit: I see, toggle the CC on and off, not toggle between CC and trash. Still, would be much handier in the lower left with one tap than accessing a menu.

Seriously! In the iPad update you add the garbage can at the expense of being able to get the big control keys circle off screen? I use that less than 10% of the time, want it gone the other 90%.

My first impression using Designer v2 was WTF, especially with regard to the the function key button. It seemed a little retrograde to put keyboard shortcuts on a touch device. But it didn't take long to adjust and the consequence is expeditious indeed, at least for those of us used to the shortcuts on the desktop! You've basically enabled fast two hand operation for pencil users; pencil in one hand, toggle thumb and fore finger with the other. Have yet to dive deeply but this ease and the cleaned up interface are worth the upgrade.

As an example. I have a Designer file in the File folder/app on iPad, then open that file in AD. After making many modifications, I save the file, assuming it is being saved to Files. I then rename the file in AD and save it. The expected behavior is that I will now have another file in Files with that new name. No. Any new changes I have made to the file since renaming it have now overwritten the original file in Files where there is still just one copy with the original name. The file in Files and that in AD are linked but they have different names. This should not be. After experimentation, I realize the proper process for this is to, within AD, Duplicate the file, change the duplicate's name, then save it. (Or duplicate within Files, change the name, then open in AD.) Can do. But still I find it disturbing the same file would have different names depending on its location. If the file's name is changed in AD, then saved, the name change should be reflected in Files as well.

Honest! I looked there but missed it. Thanks. So, how do I turn it off? (Just kidding.)

Working in Designer on iPad. Is there a way to get rid of the huge "Tutorials" link on the page that displays one's files? Maybe the same for "Samples"? I treasure an uncluttered space, not sure why this must occupy the real estate it does.

Your video certainly confirms what I see typically. The one intrieging suggestion is a modifier key on my iPad effecting control on my desktop. I can't begin to imagine how or why that would work. I've never ever seen an app on a device interact with one on my desktop except through intent involving a series of operations. I am currently past the design phase of my project so am not using AD of late. If I see this behaviour again I will post back here with, hopefully, more germaine information.

Hi Dan, thanks for the response. It's been a few days since I've used AD but I don't think I was using any modified keys to elicit this behaviour. In fact, the behaviour seemed weird because I wasn't using the Option key. I wasn't able to make this happen predictably, it seemed aparently random but not infrequent. One thing I tried was noting where I grabbed the tangent handle but that didn't seem to be it. I suspect this is part of an attempt to streamline working with points and when I figure it out I'll like it. Edit: Upon just investigating, the Node Tool interface appears as before 1.9. When the issue was occuring, somtimes tangent handles, or maybe points themselves, would appear magenta. Could this mean I had triggered some ancillary mode introduced in 1.9? (I realize this also happens when a cusped tangent is manipulated to be in-line with its partner.)

I've just noticed this recently, likely related to v. 1.9 but I'm not positive; maybe I accidently engaged some previously unknown "feature". Often, when I now select a tangent for a point on a curve, that tangent is cusped, not linear. Even if the tangent is linear across both handles it immediately becomes cusped, non-linear, when I move one of the handles. This is not because of any intent on my part. It used to take a deliberate action, holding down the 'option' key while dragging, to break the linearity between both handles. I also notice the point and handle being moved become purple when the two handles are linear, letting up at that point will again make them linear (fine by me). This is new to 1.9 so I suspect the issues I see are as well. I suspect there is a setting or something else I should be doing to obviate this non-desired behavior?

Thanks! I was unaware of this page. I can't explain why but, after viewing the link you sent, I tried again within AD and got a proper search result.

After installing AD 1.9, I went to "Help" to see how to use it. Searchng "Contour tool" yields not a single reference to it.

Thanks for the help. I do not use iCloud and I had not backed up the iPad since creating these files, no on auto-update. However, almost all the files were iterations of the same project and the salient file was backed up to my desktop. So, no great harm. I may have installed an update but don't remember reinstalling. But I'm now curious about the role of the iOS 'Files" app. While researching this issue, I read that the files ("on this iPad") stored within the Files app are merely pointers to the actual files which are kept within the originating program. (This info was a few years old.) But when I would save a file from AD into Files, then remove it from AD, the files would appear to be in Files but not within AD. I guess this is misleading.

Thanks for the feedback, Walt. I've only ever had one Apple ID. The App Store recognized that I possessed AD, the Get button read as Open. . . until I trashed AD. As mentioned, I hadn't emptied the trash. I actually have the interface mostly back at present, I just had to, item by item, re-populate the screen with tools and panels. But I still haven't any text in some buttons although they function when pressed. Just hope my memory holds out on what they do until the next release. Pressing Tab didn't dawn on me, duh. Full window is not a function I ever use on my big desktop but I do on iPad although not with Tab. But you're correct, I suspect that would have done the trick. It also didn't dawn on me because I was linking the missing tools/panels to the missing button text which is still extant. It still unnerves me that I can't reinstall the app if I need to without resorting to a re-purchase. Now I wonder if the App Store will try to charge me for the next incremental upgrade although I hope that may be keyed to recognizing its presence on my Mac.