ideally - we should be able to add a feature that allows you to open up the email client, send a file, then close the email client, all without having to leave your app.
it is on the todo list. no ETA.
c.
[import]uid: 24 topic_id: 12957 reply_id: 58239[/import]
Joshua a function like that would be great! I understand that it can be hard to create that to work across multiple platforms, but it would be worth it in the end 
I’ve started making a fair few business apps recently, and all of them would benefit from that! Especially the invoice/quoting app I’m currently working on.
The reason why I didn’t use smtp like you stated above was due to the fact that the user would have to enter in most of their email details to get it to work… And even then I doubt many of them would know the needed port and details for it to work for them.
Good luck, and thank you for having it on the to do list 
[import]uid: 69826 topic_id: 12957 reply_id: 58242[/import]
Alright, so given that this may be coming but “forever” into the future… I’ll rehash a suggestion to anyone’s who STUCK – It’s no ideal solution, but it could work.
Let’s assume we have a hosted web server with PHP that has the built-in ability to send email. Most all web servers do this.
“So and so has sent you the following attachment from the Way Cool Email Sending App:” …
… That PHP upload script that receives the binary file should be pretty easily modified to send the email (for anyone with a bit of PHP seasoning). (You could incorporate some basic anti-piracy stuff in there, like having the app also send the file size of the app binary – your script could ignore calls where the app’s binary size does not match the known size from a valid install.)
For example, @jammydodger300… your server could easily send the email FROM “invoices@yourappdomain.com” … you could set the REPLY-TO in the email to the person who sent the email.
If you generate a pretty standardized email on the web server, you really can eliminate the spam-ability of it. You’d be mailing a template and filling in the blanks from the app. This would not give someone free range access to an email sending mechanism.
In any case… I’m just pointing out there are ways to accomplish “something” for those who need something now. Obviously the best solution would come from ANSCA … But Carlos has just confirmed the “best solution” has NO eta.
[import]uid: 13859 topic_id: 12957 reply_id: 58298[/import]
I noticed awhile ago that display.screenCapture() renders a grey box where the safari window should be if you have a native.showWebPopup() on the page. Any idea if that’s been fixed?
Thanks,
Scott
[import]uid: 19193 topic_id: 12957 reply_id: 58300[/import]
Scott,
Functions display.captureScreen() and display.save() are unable to capture native fields such as web popups, text fields, etc. These functions are only able to capture what is rendered in OpenGL and not the native fields that are overlaid on top. It’s a limitation that we’re stuck with and based on what I’ve read on the Android platform (not sure of iOS) I don’t think there is a way around this limitation. [import]uid: 32256 topic_id: 12957 reply_id: 58400[/import]
Joshua, any more news on the email attachments ? This is a much needed feature with the app I am building as well. Your example above would work for me but of course multiple attachment capabilities would even be better. Thanks , Craig
[import]uid: 79594 topic_id: 12957 reply_id: 63821[/import]
Craig,
We don’t plan on adding an e-mail attachment feature into the upcoming release, but it is on our to-do list for a future release. There is enough demand for this feature to up its priority.
The single file attachment is a limitation in Android. I agree that it is inconvenient. Would adding the ability to bundle multiple files into a single zip file help any? [import]uid: 32256 topic_id: 12957 reply_id: 63847[/import]
“The single file attachment is a limitation in Android. I agree that it is inconvenient. Would adding the ability to bundle multiple files into a single zip file help any?”
That would be great!
I am sad to see that e-mail attachment is not going to be there. Our app in the store now, has bad reviews because we dont have this. We cant even do the other version of the app suite without this. We are losing alot of money and customers.
Can you provide even a work around or a beta functionality? even if it is just for iOS that would be good.
Thanks,
Willy J.
[import]uid: 66859 topic_id: 12957 reply_id: 63853[/import]
Willy,
I’m sorry to hear that you are losing sales/customers over this. Right now the Ansca team needs to address its current commitments for the upcoming release before making new ones. I’ll definitely push for an e-mail attachments feature for the next release, in which case a beta version will become available to you via daily builds. You’ll likely get this feature on Android first since most of the code is already in place on that platform. [import]uid: 32256 topic_id: 12957 reply_id: 63854[/import]
Okay…
[import]uid: 66859 topic_id: 12957 reply_id: 63856[/import]
Thanks all. even a zip solution for Android for multiple files would be great. Anything would be great. The app I’m prototyping (focusing on iOS btw) for potential deployment is for insurance claims - the app allows the user to capture images of an accident scene for example and email those as part of the insurance claim. I appreciate the quick response btw… thanks.
[import]uid: 79594 topic_id: 12957 reply_id: 63876[/import]
+1!!! [import]uid: 40033 topic_id: 12957 reply_id: 65352[/import]
… From 689:
“Core: Fixed display.save() where it may miscapture the object by 1 pixel.”
WOOHOO. I’ll give that a try sometime this week and see if it solves the problem discussed way, way up there in this thread. Thanks!!
~~Kenn [import]uid: 13859 topic_id: 12957 reply_id: 69181[/import]
Nope … still fail in build 695.
I bring in an image that’s 494?×?367 … It’s 1 pixel short on the right side and the left side has a 1 pixel black line down the left.
I think it’s also cutting an extra pixel off the bottom, but that could be a fail on the scaling function to get it under screen size.
I can email anyone who’d like to try a copy of the example image I’m using … and if anyone can give me working code to load and save that via the photo library system, I’d be a super happy camper.
[EDIT to add: Using iPhone 4S, iOS 5.0.1]
[Another Edit to add: … And just to clarify/confirm … When I load the picture, it shows up fine on the screen… It’s the action of display.save’ing the image / image’s group it that causes the black line/lost pixels.]
Thanks,
~~Kenn [import]uid: 13859 topic_id: 12957 reply_id: 70440[/import]
Hi Kenn,
I’ve heard (not confirmed) that the Corona Simulator for OS X will be 1 pixel off for display.save() too. Based on my testing, Windows and Android does not have this problem. Would you mind confirming if your app has this issue on Windows and Android if you can?
Also, feel free to write up a bug report via the “Report a Bug” link at the top of this web page. You’ll be able to attach a sample project to the bug report. This way we can reproduce the issue on our end in case we’ve missed an edge case where this 1 pixel off nonsense is still happening.
Thanks!
[import]uid: 32256 topic_id: 12957 reply_id: 70459[/import]
Hi Joshua,
I’m using iOS 5.0.1 on an iPhone 4S – (but I can confirm the bug occurs both on the iPhone and Mac OS X lion.)
… I’m not a windows guy (thank goodness)… and this is not an Android app – especially important since iOS apps outsell android 40 to 1.
So *shrug* ?!? Does that mean there’s not going to be a fix for this for Apple products? I’m sorta confused by the response on this.
Can we revisit the simple ability to just directly save an image in it’s original format? This was mentioned by you and discussed in this thread about 5 months ago. Any movement on that simple concept would be beyond superb.
Best,
~~Kenn [import]uid: 13859 topic_id: 12957 reply_id: 70478[/import]
… Bug #3316 submitted… include sample code and sample image.
It’s acting slightly different in the sample… but I think you can get the gist of what I need to do from the bug report.
I’m just looking for a way to make both the imported and the saved image the same … including NOT cutting off parts of the image.
Appreciate any help or solutions.
~~Kenn [import]uid: 13859 topic_id: 12957 reply_id: 70484[/import]
Hi Kenn,
It turns out this was a bug on all platforms (Mac, Windows, iOS, and Android). I gave you details on the bug report that you filed. The bug fix will be made available in build #697. [import]uid: 32256 topic_id: 12957 reply_id: 70519[/import]
“I WILL LOVE YOU FOREVER…”
[import]uid: 13859 topic_id: 12957 reply_id: 70521[/import]
Would you mind rotating that image and checking on the issue for a vertical odd pixel? In one case I get a black line… in the test code you sent back to me, it’s getting shaved by 1 pixel.
But SOOOO close. So close. Odd # width seems to be good to go. [import]uid: 13859 topic_id: 12957 reply_id: 70737[/import]