IOS iWork Numbers Feature Request: Generic Export

Files can be imported to numbers easily from any app that supplies the right file types. Can we not get generic export functionality to send it back to any app that can receive the correct file type?
he lack of this feature severely limits the usefulness of this app. While you're about it I might be inclined to use the other iWork apps if they also included this feature. Right now I'm regretting downloading numbers and won't be getting the others.

The best place to post feature requests is
http://www.apple.com/feedback/

Similar Messages

Feature request - Vector export for all CC customers (free or paid)

Hi.
This is a fantastic tool, that can replace or add really much to the field already covered by Adobe Ideas. It just need to do all the job as Ideas do: export a professional and useable vector file.
I understand the need of prospecting more customers to the CC service, but it can be done in several other ways. As a professional illustrator, and a huge user of the iPad as a creative tool, not always I need to rely on Adobe Illustrator to finish any job (when I need of it, is just for type work, and I am already using a CS6 version for it, with no intentions - read $$$ - to change for CC by now). My suggestions are:
a. the addition of this simple export feature (maybe even by e-mail as Ideas do), for free - it would be really kind of Adobe's part ;
b. not being possible this feature addition for free, make it a paid app, but complete in terms of export options;
c. or include the vector export feature as an in-app purchase (in both cases I would be paying for it without thinking twice, and I'm sure many other people too).
That's it. I hope this little - but EXTREMELLY IMPORTANT - request could be implemented as soon as possible in a future update.

Adobe is the worst tech company on the planet as far as treating their customers well. I've unfortunately been using their products since Illustrator88 as they've been industry standard. I've paid exorbitant amounts to keep the Adobe upgrade extortion ring going. And now, they'd suggest we "upgrade" to IllustratorDraw from AdobeIdeas, crippling the best feature the app has–the ability to export vector art for refining elsewhere. This has actually become a part of my workflow so I'm not giving up Ideas any time soon. As much as I like the new features of Illustrator Draw, they are USELESS (Hear that Adobe?) without the ability to export vector art.
Thanks for another collective poke in the eye, Adobe. If there's any justice, the $50 AffinityDesigner app will unseat you as emperor soon. Affinity Designer - Vector art & design

Feature Request: Metadata Export to Sidecar Files

I want to be able to export an image file's metadata to a sidecar XMP file that is named after the image file but with an .xmp extension. For proprietary raw files, that's the default. For DNG files, I can tediously force it by locking the file, loading it into Camera Raw, and selecting the "Export Settings to XMP" function. However I want to do this for several hundred or some thousand image files at once—so loading them all into Camera Raw just to make it export the metadata is not really a feasible method.
Worse yet, for JPEG files exporting the metadata to a sidecar file is not possible at all, as far as I can tell. When the JPEG file is writable then the exported XMP metadata will go into the file itself. When the JPEG file is write-protected then Camera Raw will entirely refuse to export the XMP metadata. This behaviour is inconsistent with other file types, as Camera Raw will happily export the XMP metadata to sidecar files for write-protected DNG files. By the way, there is another inconsistency between write-protected DNG files and proprietary raw image files, as Camera Raw will export XMP metadata for both into sidecar files but Bridge will export XMP metadata to sidecar files only for proprietary raw image files but not for write-protected DNG files. That doesn't make sense.
If an image file is write-protected then any changes to the metadata must go into sidecar files—as simple as that. Why are proprietary raw image files, write-protected DNG files, and write-protected JPEG files behaving differently in this respect? Sidecar files are fully supported for proprietary raw files, half-way supoorted for DNG files, and not supported at all for JPEG files.
Anyway—I need a way to select an arbitrary number of image files of any kind (in Bridge, not in Camera Raw) and then export all their metadata to sidecar files, one sidecar file for each image file, at the push of a button. It would be nice if I weren't forced to tamper with file locking first, just create those damn sidecar files when I'm asking for them. I'd even be happy with a createMetadataTemplate() or saveMetadataToSidecar() function in Bridge's scripting interface. There, I found a function to load a thumbnail's metadata from a metadata template (i. e. an XMP file; see applyMetadataTemplate() function)—but no way to save a thumbnail's complete metadata to a metadata template. If there is a way then please tell me. If there is no way yet then please provide one as soon as possible!

Curt Y wrote:
My first question is why you want to export metadata to sidecar files. With DNG one of the touted advantages is that all the metadata is written to the file and no XMP file is needed or created.
This actually is a disadvantage that keeps me from using DNG format. XMP sidecar files are extremely useful to transfer updated metadata from the working set to the backup archive. Sidecar files do make life a lot easier.
Usually I will download the memory cards' contents to the computer's internal hard disk. Then I will add some bulk metadata, rename the files, and make a backup to at least one, preferably two external hard disks. Then I will continue working on the images—refining captions, adding more keywords, add labels and rankings, apply ACR settings. Finally I'll want to update the metadata in the backups. With sidecar files, that would require the transfer of kilobytes. Without, I'll need to transfer gigabytes because I'm forced to update the whole image files when actually I only want to update the metadata ... just because Bridge is too dumb to let me export the metadata to sidecar files. Or actually, it does let me export the metadata to a sidecar file—but only for one image file at a time which is totally useless when I need to update the metadata of hundreds or thousands of image files.
The DNG format does support sidecar files. DNG files can have their metadata internally 'under the hood' or externally in a sidecar file. When there is a sidecar file accompanying a DNG file then Camera Raw or DNG Converter will read and use it just as they would for proprietary raw files ... that's very convenient. Only Bridge doesn't allow the user to take advantage of that flexibilty but forces him to use internal metadata always, whether it makes sense or not.

Feature Request: View exported PDF when packaging

Part of my workflow on job completion / sign-off is to package my InDesign document [File > Package]
I use this feature to ensure I have fonts, links, IDML and Print-ready PDF for archiving purposes and saw that CC greatly improved the packaging feature by adding IDML and PDF options. What I would like to suggest/see is that the PDF option comes with a "View PDF File" when packaging to ensure it has saved correctly / without error. (Indesigns uses the last settings to determine bleed etc. irrelevant to which preset you have selected). It would just save a few more nav clicks along the way.

There are a couple of ways you can view the mp3 path. (1) Right click on the track, and select "Show Song File." (2) Right click on the track, select "Get Info" and look on the Summary tab.
Windows XP

Feature request : import/export .idea files with ITunes

I know that you wants to developp your own cloud system but a possibility to import or export idea files between the mac and the Ipad would be very usefull for me. Thanks

Yes Ma'am you are misunderstanding. In my case, because of a botched screen repare my ipad now has No wireless connectivity at all. The place that replaced the screen is over 70 miles away. Being as unlike Photoshop touch which has the option to sync projects through iTunes. I can not get the vectorized verzions of my Adobe Ideas projects off my device.
It really should be a simple update to the app. Which would be far cheaper for Adobe to implement, than me buying a new ipad. All my other apps that allow me to crreate content allow for itunes syncing of projects.
Then even if my ipad still had wireless connectivity some projects could easily be over the email size limit.
What would really be the ultimate answer to this issue would be on device syncing between Adobe Ideas and Photoshop touch. Just like can be done with Photoshop and Illustrator.
Adobe has to realise that the app market really is more profitable than their computer program market. Being as many many more people WILL pay the smaller price. Which opens up their market to way more customers. Add in the new ipad air's 64 bit architeture, and it's almost (almost not entirely) more advantagous to push the apps to full Adobe master collection status, and ability. It's almost a no brainer, being as it's much mich cheaper for anyone to get an ipad, a good palm canceling stylus and some apps. Than it is to buy a computer, a Cintiq, and Adobe master collection. Oh, but, if after going the cheaper route people got use to using and creating with the apps, they would be far more likely to then get all the more expensive counterparts. Though one has to see that by Wacom putting out their own tablets, the touch screen tablet market is the most cost effective and highest unit moving market.

Feature Request for Adobe Camera Raw CC

Cinema DNG Videographers / Cinema Photographers using ACR to debayer footage...
Feature request to export / save video files directly from ACR - - > Option to create video files with fps.
Note: The option to export video does exist within the main menu of Photoshop. However, this does not apply to image sequences when imported into ACR.
Uses:
Current workflow for using ACR requires applying color correction and/or image presets to footage in order to process DNG image sequences.
When shooting Cinema DNG files the image sequence is likely to be hundreds or even thousands of photos in length. These files could be processed with ACR and no other application.
Adobe Media Encoder does not accept 16-bit Tiff sequences (CS 5.5).
AE and Premiere CC accept 16-bit image sequences.
Why import into AE and CC just to set FPS?
Why import into AE and CC just to export proxy files & additional video files?
May be a very applicable option for 64-bit & 256-bit background processing?
Why make this feature applicable?
ACR is remarkable at debayering DNG images.
ACR processes DNG files faster than AE.
ACR enables user color-correction presets as well as secondary Look Up Tables (LUTs) to be applied to image sequences (potential investment for Kodak, Fuji and other color-correction houses).
ACR has the potential to offer users the ability to acquire a single application for processing DNG image sequences without having to purchase an entire post-production software suite.

Hi! Moved to the correct forum.
There is also the http://feedback.photoshop.com site.

A feature request for iOS app developers...

Guys and Gals,
I have a feature request which I think will benefit iOS app developers as much as it would benefit your customers.
Any customer that has more than a handful of apps will eventually forget what some of those apps do or what makes them unique. For instance, I had not used the wonderful hotel finder, Oyster, in over a year. I not only forgot I had it, I also forgot how Oyster's service was different than other hotel finders. I had to refamiliarize myself with the app. Sometimes, this requires returning to the App Store to read the product description again.
It would be helpful if every app had an About button that would present the product description, summarizing the app's purpose and what differentiates it from similar apps without going into the details of how to use it.

Apple discourages the use of About or Help buttons.
Send feedback to Apple because this is the wrong place to ask; we are all just users like you.

Feature Request // Book Module: Export as indd file and management

Book Module: Export as indd file and management
I would like to request a feature to export a book module as indd file.
I like PDF's but .indd is nice also so we are able to to more in depth layouts.
Having Lightoom being able to manage all your pictures and book layouts would be nice, alot of things can be done in one application.
Another Feature: Using Lightoom as book layout management.
Being able to send a page(s) of the book from lightroom into InDesign to do indepth layout and editing, then being able to send it back into lightroom
Almost similar to how you can send a photo from LR in Photoshop to do indepth editing and then send it back into lightroom.
This could and will ease the workflow of book management and layout design. So lightroom will not only be able to manage photos, but also indesign and book layouts.
http://forums.adobe.com/message/4238530#4238530

Why do repeat it here, as you have already filed a feature request for it?
BTW AFAIK this is already implemented: you can use Adobe Illustrator or InDesign or Opensource Scribus to edit layouts.
They are just not ready to publish how - another sign of the quality processes at Adobe.
But you do not send from the book module.
You create upfront layout templates, which you can import for use inside LR book module.
This is a one-way street.
The book module designers did not acknowledge a use case where you might want to fiddle the exact placement of really chosen images.
It is always you first design a template, then use it.
Love it or leave it - *change it* is not an option that Adobe seems to give to their beta testers.
Cornelia

Feature Request: Make a Setting Option for Export - Media - What to Render

As I just changed after many years with Premiere Elements to Pro, I certainly find many things just anconversant.
But there's one thing I really can't take: When I'm trying to render a project, there's a small selection list near the bottom of the "Export Media" window saying "export area". Here I can choose between "complete sequence", "work area", "sequence in/out" and "defined by user". This option jumps always back to "work area"!
That's at least for me very unconveniant, because in 99+ % of my renderings, I need "complete sequence". Normally the software remembers the last used setting, but not in this case. I can imagine that one can fight about what's the best default setting: I Guess everyone is using Premiere differently. So in my opinion a predefined setting option would solve best for all: Just add one mor setting in the Presets section, maybe in "General" or make a new rubric "Export" or something. Just a place where everyone can predefine which setting for the export media area option he likes.
No big deal, just one more presettings option!
I hope I could make myself clear what I'm meaning
Thanks in advance!

Hi Lutzz,
When I'm trying to render a project, there's a small selection list near the bottom of the "Export Media" window saying "export area". Here I can choose between "complete sequence", "work area", "sequence in/out" and "defined by user". This option jumps always back to "work area"!
That's at least for me very unconveniant, because in 99+ % of my renderings, I need "complete sequence".
You can create a feature request here: http://adobe.ly/feature_request
Thanks,
Kevin

IOS 7 feature request: Option for home button to home not folder.

IOS 7 feature request: Option for home button to home not folder. Maybe for some this workflow is good but not for me. To many clicks. At least give the option to have my home button take me to my home page. 9 times out of 10 that's where I want to go. Not back to my folder.

send your feedback here http://www.apple.com/feedback/

Feature Request: Export catalog for 2nd editor/machine

Since there isn't a shared network environment for LR, to involve multiple editors or multiple locations for the same editor on large projects, I often need to export a subset of a catalog so someone else can work on it, or I can work on it off my laptop somewhere other than the studio, using only the proxy 1:1 previews to make my decisions from and then re-assimilate those edit changes to the master catalog of that job, usually back on my primary workstation. This process also allows me to start processing out parts of the job while other parts are being edited on other machines, or letting my primary workstation process while I use a 2nd workstation to continue editing at speed on.
I can make this happen, but it's all on me to remember which portions of the catalog have been exported, where their destination was/is, remember not to make any changes to that portion of the library while the subsection has been exported, and an over-lengthy and complicated merging of exported and internal catalogs.
It would be incredibly useful if LR could show the status (checked out for primary edit, checked out for client approval, etc.) of any exported catalog by mousing over that visibly different section and build in a preference for those varied conditions to potentially limit any changes to that subset of images while the export is still 'checked-out.' A true merge would be nice to allow possible overlaps of work on the same images, but a managed lock-out would be sufficient to start with.
As it is, the re-assimilation process for me involves removing images from the master catalog leaving the raw files in place, and re-importing the exported catalog which also necessitates the needless redundancy of bringing the 1:1 previews back in as well. At the scale I'm doing this it's overly time consuming, compared to the speed of just bringing in the library itself. The process also puts me in the place of deleting images from a catalog while they're essentially still in use, which is scary from a file management standpoint, usually with me having 4 and 5 copies of that library lingering around until all the manual merging actions are finished.

That's a feature I've asked for myself Brad, in the absense of true network use. As it's not likely to make the final release, and we wouldn't want the request to get lost in beta land, might I suggest adding it as a suggestion on the Feature Request forum http://feedback.photoshop.com/photoshop_family where it can easily be tracked? If you post the link to your request here, others can also vote on your request.

Feature request - Non-destructive export to Photoshop Touch

It would be pretty nice if we could export .idea files into Photoshop Touch as a layer (like a smart object in Illustrator/Photoshop) and link the file so any future edits would be reflected

Why do repeat it here, as you have already filed a feature request for it?
BTW AFAIK this is already implemented: you can use Adobe Illustrator or InDesign or Opensource Scribus to edit layouts.
They are just not ready to publish how - another sign of the quality processes at Adobe.
But you do not send from the book module.
You create upfront layout templates, which you can import for use inside LR book module.
This is a one-way street.
The book module designers did not acknowledge a use case where you might want to fiddle the exact placement of really chosen images.
It is always you first design a template, then use it.
Love it or leave it - *change it* is not an option that Adobe seems to give to their beta testers.
Cornelia

Feature Request: Several Key Items

I am not really new to DPS. Have been publishing under contract for my client for the last 2 years now and it's been going great. However, there seems to be a few things we wish for that we can't seem to do. I figured this is probably the best place to request these features, I'm keeping my fingers crossed that somehow these make their way into an update or are considered maybe for other program features (you'll see what I mean later when I get into it).
1) It would be nice if we could produce apps for android phones as well as tablets. I am more of an iOS guy but we do have a bunch of users who want to access these folios on their phablets and android phones but cannot get access to it. I don't know how complicated this process might be but it would be a great feature to add in any upcoming DPS releases.
2) We are using DPS for publishing but we have been requested to use it in an "app style". The client wants this because they are comfortable with DPS and happy that their staff can use pretty much all the adobe suite programs. Maybe an ability to disable the browse toolbar (where the thumbails for articles show up and navigate). This way we can create a single page with MSOs and trick the user into thinking they're in an app instead of a digital magazine publishing platform app. This would work great for companies that want an app to accompany their magazine and display info about the company, how to reach them etc instead of having certain pages within the magazine.
3) A muse widget. I would love if we could directly export muse files directly into DPS (say, as if we were importing an image). I know this may be much to ask since this isn't the Muse feature request board but it woudl be nice to be able to export it as a widget that will automatically package it into an element with all the required files to import into DPS.
4) As muse and DPS are both great apps for designers who don't know how to code, maybe one or the other, or creating an app that is based off of the two could be an excellent choice for deisgners. There is a huge gap in the market for app builders. Muse is mainly a web builder and DPS is mainly for publishing. I think if Adobe could maybe mash the two into an app that helps users build basic apps. Imagine being able to make an app the same way you do in DPS? Having preset widgets such as capture image from camera, use geolocation, upload to server or whatever. I'm not too verse in this but it'd be nice if I could use an Adobe app to build an app that wasn't just a digital magazine. Maybe my lack of knowledge in this area is simplfying the whole process so forgive me if that's the case. From a business perspective it just seems that there is a huge gap for this, and maybe Adobe can conjure something up for the Adobe Faithful.
5) Automatic web viewer. Would be nice if whatever displayed on my iPad can automatically shoot up into a web viewer linked to a business catalyst account or a specified server as an HTML5 file. Again, I haven't gone too much into the web viewer version so forgive me if this already exists, but I have looked through some documentation and not really found much on it.
6) WIDGETS! More widgets like muse would be a life saver! Maybe something like a slideshow instead of just having the MSOs fade in and fade out, maybe allow a widget to do a slideshow that snaps into place everytime you swipe. It seems more natural since a lot of the apps function this way. Widgets also open up a lot of doors, maybe allowing users to create their own widget and housing a widget library on the adobe website?
Just some thoughts, not sure which ones are really doable but I figured it's worth a shot requesting them.
Thanks for your time!
Best Regards,

Adobe - Wishlist & Bug Report
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Delivering on your top feature requests!

Dear Adobe EchoSign community --
As Fall starts to settle in, [at least in the Northern Hemisphere], I wanted to share progress we've made on your feature requests. As context, our team sits down weekly to review your top feature requests that come from our community sites, our support, and our 1:1 conversations. Year to date, we've already delivered more than 80 of your top feature requests: Enterprise administration, API flexibility, improvements to our fields and more.
A partial list of the most-requested features delivered include:
Refreshed and new clients for Android and iOS
New sign-only role : control who has signing privileges, and who can send agreements
Batch user creation: enable/disable accounts
Ability to update & edit your published widgets
Advanced data retention policies and configuration
Field alignment & form field sizing during form authoring
Text Tags for creating hyperlinks in documents
Specify text color, font and font size for form fields through text tags
Repeat fields at the same location with the document via text tags and form authoring
EchoSign signature stamps on documents through text tags and form authoring
EchoSign Transaction ID on documents linked to the EchoSign Audit Trail through Text Tags and form authoring
Field labels for radio-buttons, check-boxes and links from text tags
Enable/Disable form fields through conditions during e-sign
Enhance reporting to export read-only metadata included with the agreements
And a huge amount of work with the REST API Set:
Sending documents with phone authentication
Creating widgets with multiple counter-signers
Replace signers through the API
Allow signature delegation through the API
and more.
Over the remainder of the Fall, our key focus areas include the new Salesforce1 release, expanding our enterprise administration capabilities, building out the REST API, and the constant work on the SaaS infrastructure to increase performance, availability, and security. We have more to here.... we know! So keep the feedback and ideas coming. And thank you for your engagement and use of Adobe EchoSign. Hope to see you at Dreamforce '14.
-- Jon "JP" Perera

Evita,
Yes, you can still vote on Accepted. (You can even vote for "Scheduled for release...", because sometimes we need to move features from one release to the next)
Accepted means that it sounds feasible to do and we can do it, but "when" has not been established. Please add votes to help that decision.
Rejected Just that, we have no plans to do this. I don't revisit rejected on the Exchange.
(However, some features that have been rejected have been discussed on the forum and we've reconsidered. We have also changed "rejected" to "accepted" on previous occasions, but only based on discussions here. Some features rejected have very poor explanations as to the problem users are trying to solve)
Open We haven't read them or made any decision on them.
Awaiting Community Votes means just that. Someone has proposed a feature and no-one else seems to be interested.With the long list of features, we do need to prioritize and some features requested are obscure, so we want more feedback from the community. More votes and feedback from the community helps. We sometimes get 10 points from some folk and zero from others for the same feature.
Please note that except for the Open features, the others we have touched and added feedback.
Problems I have with the feature requests is lack of clarity in the request and more than one request described in a single request. The extra features get lost and others can't vote on them.
Sue

Multiple Imperative Feature Requests

I am a MN Photographer and have been using PS Lightroom through 2 betas and 2 release versions. I have been amazed at the improvements Adobe has added, but from my point of view, they need to add a few more features to make LR more robust and efficient!
I love the way LR makes terrific web galleries!
I am running LR from a Seagate Barracuda 300 External Hard Drive with Firewire connection. I am using a Mac Powerbook (1GHz Processor) with 60GB HD and 55% free, w/ 2GB DRAM, and an Apple Cinema Display. I can't complain about slow downs, but keep my permissions tuned once a week, both on the Mac PB and all EHDs.
LIGHTROOM FEATURE REQUESTS
1. From the Web module, there is only one option for adding Copyright Info to images in the Web Galleries, either ON or OFF. It would be a great addition to have this option variable by type size, type placement on images, and opacity. I last generated a web gallery and some of the images said, "2007 Alex Bachnick All Rights Reserved," but many of the images said, "Alex Bachnick All Rights Reserved," without a year. A few images said, "Copyright 2007 Alex Bachnick All Rights Reserved," like it is supposed to! The LR application has been inconsistent so far in this area. By adding a line of copy that can be saved, and by varying the opacity and placement on images would be a huge step forward!
2. It is IMPERATIVE that you embed metadata into the Web gallery images. This is primarily for adding keywords and copyright information, but LR is inconsistent so far. Sometimes metadata is preserved, but it doesn't always get embedded when exporting images.
3. When I generated a Flash Web Gallery, some of the color was good, some of it was terrible. I have suggested before that you write into the action that takes the original image, reduces it in size, then convert to profile from Prophoto to sRGB. I suspect that you have a script in there "Save for Web". This script is denigrating the color when Convert to Profile would preserve the color. Admittedly Safari is the primary web browser I use, and it's color-centric, whereas most of the others IE, Netscape, and Mozilla, aren't.
4. When I use HTML for the web galleries, the color is spot on, but a young friend told me it would be better to hit one button to go through the images as in a rapidly advancing slide show, rather than hitting each image, and then wait for it to enlarge. This could be another marked improvement, if you made the output a slideshow from the Web Module.
5. I tried generating a slideshow from the Lightroom menu, and had about 200 images in a collection. The application went through the motions, but I tried opening the slideshow but it didn't work. I tried it in PDF format and it output a 135MB file that ADobe Acrobat couldn't open. It is still not working. I have also used a third party application Photo to Movie (www.LQGraphics.com). This is a $50 application that you can add music to and vary the zooms and dissolves and this works incredibly well!!!
6. One of my biggest problems so far is the sort mechanism. I have about 9500 images in my library, and about 5% of those were made from about 2004 and on. My images are sorted by "capture time," but the images shot back in CY 2004--2005 are mixed in somewhere way down in the pile. There are some bugs in the program for reading the capture time, and so far this is not working accurately!
7. From the Lightroom Library module, several times I have exported images for 3rd party needs and the application puts out varying results. In March I output some images for Communication Arts magazine. They specified file size and format, and it took me several times to export the images to their specifications. I recently exported some images for submission to a UK based stock photography agent. The images came from 5 different cameras~~Hasselblad w/ Imacon Digital Back, Kodak DCS-14, Canon 1ds MkII, and Canon D-20. There were 10 images that needed to be output as JPEGs (

1. LR uses what was written in the copyright field so it's your data entry that is inconsistent.
2. Are you 100% certain this is not working reliably under 1.1? It definitely wasn't working at all under 1.0 and Adobe responded to complaints. Since 1.1, I've taken large numbers of Web-generated pictures into iView and not found any cases where the metadata was missing. "Sometimes" is too vague. How exactly can you prove it? What programs prove it?
3. Not sure, but isn't this a problem because of Flash? Also the browser you use is not important - it's the browser that your visitor uses that you need to focus on.
4. Realistically, Flash is better for this. You can always get someone to write/modify HTML templates to do such a slideshow, but the built-in templates are already very complex and this suggestion would add another layer of browser incompatibility.
7. This isn't a feature request. Raise this in the main forum - and be specific (your post was also too long and got truncated). How can anyone help you if you say "varying results"? It's unlikely that any variation is random.
John

IOS iWork Numbers Feature Request: Generic Export

Similar Messages

Maybe you are looking for