JonnyPanic

That didn’t work either. In the end I did the double tap on the splash screen, and reset everything, including activation, that did get it working again.

Designer crashed, deleted all the assets and won’t re-install them, they all fail (except brushes, they install) with a missing propcol error. I’ve reset everything, and uninstalled and reinstalled (I also have publisher and photos installed) designer, it makes no difference. And the same error with photo and publisher too. Help!

No, that doesn’t give the functionality, as I said, I know how it currently works. My question is… is it PLANNNED to add the ability to load lens correction profiles (LCP/XML) into photo (V2) on the iPad, as in photo for Windows/Mac? Thanks for the response though.

Hi, is it planned to add the ability to load lens correction profiles (LCP/XML) into photo (V2) on the iPad, as in photo for Windows/Mac? …I know how it works currently, & I know I could use the Lens correction tool, that’s not the question. I’d like photo to easily support lenses it currently doesn’t, in the same way as the windows/Mac versions. Thanks.

I’ve an image, 6250x4688 that when I try to export crashes the app back to the desktop on my iPad Pro 2018. Screen recording is attached. IMG_1526.MOV

Paul, very true, if I had many tabs open on a desktop app I’d hit the “save all” button, just to be sure they are all saved, but I can’t here. I need to open each individually to be sure they are saved. (In this case saved==exported) Of course, I’ve no intention of leaving files “open” forever. I’ll continue to save each separate file, by opening, saving and closing each one, one at a time, since there’s no choice. As you say it’s been the case for 7 years, or “we’ve always done it this way”.

“The risk is that the protected files can and do get corrupted.” I’ve had a quick search for file corruption issues in the Affinity forum, and found a few relating to installation and SSD connection, none to internal memory on iOS devices, I’m not saying it’s not a “risk” (everything can, technically be described as a risk) but while the severity may be catastrophic, the likelihood of it occurring is rare, hence the choice not to have backups all over the place. I could apply the “it might fail” logic ad infinitum, and backup forever, but there’s a diminishing return. “If your preferred workflow is to not Save your work” It is to save, obviously, but in a more convenient & project friendly way, rather than a per unit way. “the loss of your device…” blah blah Files are saved to the cloud, and I also have a local backup strategy in place for originals and completed work, thanks for your concern. “Lmao. You are using a touch device…” Yip, that’s the forum “Affinity on iPad” “if you save each file as it is created you won’t notice the few seconds it took.“ Yes, yes I will. If I do something in in one shot, or broken up, I’ll still have the same amount of time out of my day, and my RSI will still be have to deal the same number of taps. ”You also won’t need a batch export function to relocate 100's of files at some later stage.” True, that’s a called a work-around, used when a required feature doesn’t work, or isn’t present. ”I’m one of the millions of electronic device users who like to have their devices securely backed up on external storage. If my devices are lost, stolen, accidentally damaged or simply cease to function, no need to panic, Jonny, I just replace them and access my 'saved' copies. Nothing lost.” Well done there, have a medal. You know ios devices (and most others) backup to the cloud automatically so there’s no need for the local backups of which your so proud, welcome to 2022. So your argument seems to be this…. Batch export of projects is not needed because there’s a workaround that shuffles the tedium around into more, smaller bits of tedium, both require the same time and the same number of user interactions, so do not solve the real issue, but…. backups(?).

Perhaps it’s an application design issue. What is this risk of which you speak in iOS’s “protected area”? Why must save files again “for security”, what does that even mean? I’m not sure there’s a whole lot of lost or damaged files being reported in these forum… if the app can’t save a file have we all invested in lemon? Users should not need to create more files outside of any stable storage system in order to create the file we need to use, that’s just crazy. “This takes a few seconds”, and (I think) about four taps, per file, so let’s simplify this… 1 file, 5 seconds, 4 taps 2 files, 10 seconds, 8 taps 4 files, 20 seconds, 16 taps 8 files, 40 seconds, 32 traps 16 files, 80 seconds 64 taps QUEUE SEVERE RSI So, don’t take the easy route and blame the user, create what they need in this otherwise great application’s. Don’t make them d*ck around in menus & click a few menu items that “take just a few seconds”. just enable.

Version 2 and still no way to quick expot a project, it cripples the work flow, we should be able to export a projects worth of files… should not have to open each individual file to export. it… just… makes… no… sense…. that… I … still…. can’t… quickly…. export…. a… projects…. worth…. of…. files…. without… monotonously…. opening…. files…. to… export…. each.

I’d settle for that, if I could do that, per “project” and not for each individual file, and then easily kill the project folder. but alas, no.

Is there any chance of implementing simplest project management into AP & AD? Since I can create a ‘project’ the concept of managing that shouldn’t be outside the scope of Affinity. Please, just let me 1. Export all in a ‘project’ as xxx 2. Close a project (& remove all in it) Is that too much to hope for?

oh well, maybe in a future release… maybe.

@Patrick Connor This sounds great… but where is it? I’ve searched but can’t find how to load an acm file in ap for iPad. help.

In the batch export dialog on the iPad… 1. The user selects n images. 2. The user selects a lens profile from a drop down in the burger menu of the export dialog 3. User exports as currently.

Thanks, its a 2020 pro. There should be validation criteria when a user attempts to open a file. If The file fails the test, so can’t be be opened the user should be presented with a message why, and AP not open the file. If it can opened then the user should only be presented the with options that work. Essentially: AP is not handling this failure mode “gracefully”.

When I open a jpg of 86MB, 20738 x 24753, I can save it a a png (403MB) but not a jpg, AP calculates the jpg file size as 0, and saves it as 0. is this a bug?

@walt.farrell “You can't select a profile” “… and on occasion that may not happen properly.” So surely to mitigate this issue the user should be able to select their profile of choice, no?

Hi… in affinity photo (iPad) … I have a document 12000 x 5000, with a background pixel layer, where I have resized the canvas to 10000 x 5000 to show only part of the background. I add an object from affinity designer (a label) it appears a new layer… all fine so far. When I merge the layers the document is now 10000x5000 - not what I need - I need it to remain as 12000x5000 with the canvas as 10000x5000 and the designer object embedded in it. Am I doing something wrong or is this a bug?

@MEBI was hoping to see the same list as here: also, maybe a better selection model than a single scroll wheel would work better.

Is it possible to manually select the profile, on the iPad? if not, why not?

@carl123, thanks, that works great. The iPad workflow is this: 1. Resize the panorama document to 10,000 x 5000 2. Run the 360 panorama macro, no scale and no alignment 3. Select centre in the alignment box, unlock the aspect ratio and then resize the canvas to 10000 x 5000

Thanks Walt, @carl123 could you please also post the the 360-panorama-macro.afmacro as a macroS file. Thanks.

Can i also get the 360-panorama-macro.afmacro as a macroS file... Thank you!

Can someone please add the macro as a macros (with an S) file so it can be imported onto an iPad. thanks!

It seems the only lens profiles available in the lens selection selection profiles are those in the apple engine, even if the serif engine is selected. is that right? is there a way to manually select a lens profile in the serif engine? a parrot Anafi in my case.