This is way outside my area of expertise, but would it be possible to
kludge up a workaround? It the problem is not importing an image >4095
wide but displaying it, it should be possible to import it, split it
into two images <4095 wide by walking through the imagedata, place the
two side by side, and display them as a group. Nasty, but at least
allows you to see the image. The problem would be how processor-
intensive and time-consuming would this be. Probably a real limitation.
-- Peter
Peter M. Brigham
[email protected]
http://home.comcast.net/~pmbrig
On Jun 28, 2009, at 1:07 PM, Mike Markkula wrote:
Sarah,
The script below will at least treat the user properly.
I too wish wish wish Rev would remove the 4095 pixel width limit!
(there is no height limit) As is, its a deal breaker for any serious
app in the photography arena.
Mike Markkula
--------------------------------------------------
function importImageFile theFilePath
-- attempt to create image given its file path
-- if successful, return its id, if not, return empty
-- Rev can import images wider than 4095 pixels,
-- but can’t display them properly
set the itemDelimiter to "/"
put the last item of theFilePath into theImageName
try
import paint from file theFilePath
put the ID of the last image into theImageID
if the width of image ID theImageID > 4095 then
delete image ID theImageID
put empty into theImageID
beep
answer "Sorry, I can't open " & quote & theImageName & quote
& \
" because it's wider than 4095 pixels."
end if
catch anyError
if anyError is not empty then
delete image ID theImageID
put empty into theImageID
beep
answer "Sorry, I can't import " & quote & theImageName &
quote & \
" because " & anyError & "."
end if
end try
return theImageID
end importImageFile
-------------------------------------
On 6/27/09 5:33 PM, "Sarah Reichelt" <[email protected]> wrote:
Which brings me to the forum question "I've got photos of 13
megapixels that
Rev can't handle". Who wants to push the (Revolution) envelope
that far ?
Me for one. My app Pic-a-POD <http://www.troz.net/Pic-a-POD/> suffers
greatly from this problem as more and more large images appear on the
internet. At the moment I am forced to check for images with more
than
4000 pixels on any side, and if so, I just have to show a notice
saying that the image is too big to display. This is not always
correct as a tall thin image can work but I haven't been able to work
out an exact algorithm for telling what will work and what won't.
Even
more unfortunately, there is no error reported when Rev tries to
display an image that is too big - you just get horrible grey streaks
or some other form of distortion.
As consumer level cameras produce larger and larger images, the
prevalence of such images will only increase and I think it is
unrealistic to say that people shouldn't be using such large images.
If their cameras can do it, why would they not take images at the
highest possible quality? This is not a problem that is going to go
away and I think RunRev need to give some serious thought to fixing
the image object.
Cheers,
Sarah
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
