datorhaexa

@Dan C Thanks for the reply! I suspected such a dependency but I don't recall this happening before. Anyway. Will see if a PDF will pass the requirements or else go an extra step through a bitmap application.

@Dan C Uploaded!

@Dan C A private upload will be good, thanks.

I'm using AD 1.10.5.1342 on Win. When exporting a file for print as a JPG, the export size (in this case with a bleed but even without, it's the same problem) is wrong. I'm not doing anything exotic, so I can't imagine where there could be a problem. A PDF export works well as long as I'm not using an artboard (because there it had problems). Generally, those export issues with AD are making it hard to move away from a spare Photoshop and that's not good for the product.

I must confirm what @Davidlower wrote regarding the added "ghost" pixels or gap when exporting. That's particularly frustrating but this is the result of AD not knowing what to do with additional fractions of a pixel when exporting, I guess. I can't imagine this being useful in any type of work, not only UI.

I'll add myself to the list of people who (after months of use of AD) miss an export preview. I work for web and size is essential. AD has tools that address retina and different dimensions of export, but all of this happens in darkness. I don't know what I am exporting unless I go and inspect it and then return and modify and export and review.. The whole Idea of automated export falls flat on its face when it's done without having an idea what one is doing. And if I have to additionally run files through other tools... Ah, really, how is this helping? So, please guys, take this more serious. Thanks!

No, I was a bit annoyed at the thread going in a general educational direction (in itself not a bad thing but there should be different places for that) and perhaps didn't express myself clearly. I still think that this constrained resize -> non-pixel size values is something that could be dealt with because general resize snaps well to pixel values without any negative outcomes. But who knows.. For now, as tedious as it is, I'll have to go and correct sizes after a constrained resize.

No no, you answered my question as far as the state of things is. This is not the solution but I understand that it's all you can tell me and do. Thanks.

The following is an anti-aliased graphic of an orange circle. In pixel size. Unlike me, @MEB had the time to answer all other questions. But mine, alas. That's a different story.

It's nice you have the time to discuss what browsers can and can't do. I came here to ask a simple, concrete question. I'm not sure what this whole tirade here is about.

This happens to be a default with Fireworks which works with vectors as well, and since I've been using it for ages and find it superb, I am trying to at least cover the basics with AD. And the ability to rely on pixel values for graphics for the web is one such basic. I guess others might use it for other stuff and that's fine. I don't need to be convinced in one way of seeing things or another, or need an explanation for what vectors are (I've done graphics with Xara in 1998). I seek solutions to concrete problems. That's all.

This is interesting. I'll try this tomorrow. Thanks!

You might be right in some of those cases, but I had to export banners (not UI, I know) these days, and when scaling the bounding box with all that's inside, I have to come to a concrete pixel value by specification. P.S. And it's not even important what use there may be if I set the setting to pixel perfect and get anything but. Then the whole setting makes no sense.

I see.. This was never an issue with Fireworks. Text scaled along. It's especially annoying for UI design, as you can imagine, and it makes it almost unusable if one want to be productive. So, yes, please bring this up to the dev team. It cripples AD for me.

But you can round them! This will be the point and especially for UI design I can't imagine this to work any other way.