Export PNG weirdness

2006-08-11 Thread Chris Carroll-Davis

Hello everyone.

Can anybody help with this ...

I am exporting PNGs from fields, using this syntax:

  export snapshot from field fname to file imgPath as PNG

This works just fine on about 30 or so fields, but when I come to one  
particular field it fails with error message:


export: can't write to file, mask file, or container

All the fields are opaque.  If I switch this field to non-opaque...  
it works fine... or if I export as JPEG it works fine!  The only  
difference (that I can see) between this field and others is that it  
is larger than the others.


Has anyone come across this problem before?  Could there be some  
other property that I have overlooked that is causing the problem?


I am pulling my hair out at this one (and at my age I don't have too  
much to lose)



Chris



___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Export PNG weirdness

2006-08-11 Thread Dar Scott


On Aug 9, 2006, at 7:53 AM, Chris Carroll-Davis wrote:

All the fields are opaque.  If I switch this field to non-opaque...  
it works fine... or if I export as JPEG it works fine!


Can you export to a field as JPEG and then export the field as PNG?   
Maybe therein lies a workaround.


So your current thinking is that it is not fonts?

Dar Scott
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Export PNG weirdness

2006-08-09 Thread Chris Carroll-Davis


Hello everyone.

Can anybody help with this ...

I am exporting PNGs from fields, using this syntax:

  export snapshot from field fname to file imgPath as PNG

This works just fine on about 30 or so fields, but when I come to one  
particular field it fails with error message:


export: can't write to file, mask file, or container

All the fields are opaque.  If I switch this field to non-opaque...  
it works fine... or if I export as JPEG it works fine!  The only  
difference (that I can see) between this field and others is that it  
is larger than the others.


Has anyone come across this problem before?  Could there be some  
other property that I have overlooked that is causing the problem?


I am pulling my hair out at this one (and at my age I don't have too  
much to lose)



Chris




___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Export PNG weirdness

2006-08-09 Thread Chris Carroll-Davis

Update:

I can of course make this work by grabbing the relevant portion of  
screen (rather than specifying the field):


  put globalloc (Topleft of field fname) into tl
  put globalloc (botright of field fname) into br
  export snapshot from rect tl,br to file imgPath as PNG

But this is a bit risky as I can't guarantee that there will be  
nothing on top of the field (e.g. floating palette) or that the field  
will completely contained on screen.



Chris



On 9 Aug 2006, at 14:59, Chris Carroll-Davis wrote:



Hello everyone.

Can anybody help with this ...

I am exporting PNGs from fields, using this syntax:

  export snapshot from field fname to file imgPath as PNG

This works just fine on about 30 or so fields, but when I come to  
one particular field it fails with error message:


export: can't write to file, mask file, or container

All the fields are opaque.  If I switch this field to non-opaque...  
it works fine... or if I export as JPEG it works fine!  The only  
difference (that I can see) between this field and others is that  
it is larger than the others.


Has anyone come across this problem before?  Could there be some  
other property that I have overlooked that is causing the problem?


I am pulling my hair out at this one (and at my age I don't have  
too much to lose)



Chris




___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your  
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-revolution


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Export PNG weirdness

2006-08-09 Thread Chris Carroll-Davis

UPDATE 2:

weep, weep.

It's the font.:-(

I haven't worked out what the specific issues are, but it simply  
fails with many, many fonts.  Don't know whether it is a problem with  
Postscript, TrueType, Unicode or what.


I suppose I should lodge this as a bug - quite serious, in my opinion  
- since the ability to output images from specific controls was one  
of the features of 2.7.2 I believe.  I've never used bugzilla before 
(!) is it simple to do?



Unhappy Chris



On 9 Aug 2006, at 15:28, Chris Carroll-Davis wrote:


Update:

I can of course make this work by grabbing the relevant portion of  
screen (rather than specifying the field):


  put globalloc (Topleft of field fname) into tl
  put globalloc (botright of field fname) into br
  export snapshot from rect tl,br to file imgPath as PNG

But this is a bit risky as I can't guarantee that there will be  
nothing on top of the field (e.g. floating palette) or that the  
field will completely contained on screen.



Chris



On 9 Aug 2006, at 14:59, Chris Carroll-Davis wrote:



Hello everyone.

Can anybody help with this ...

I am exporting PNGs from fields, using this syntax:

  export snapshot from field fname to file imgPath as PNG

This works just fine on about 30 or so fields, but when I come to  
one particular field it fails with error message:


export: can't write to file, mask file, or container

All the fields are opaque.  If I switch this field to non- 
opaque... it works fine... or if I export as JPEG it works fine!   
The only difference (that I can see) between this field and others  
is that it is larger than the others.


Has anyone come across this problem before?  Could there be some  
other property that I have overlooked that is causing the problem?


I am pulling my hair out at this one (and at my age I don't have  
too much to lose)



Chris




___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your  
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-revolution


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your  
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-revolution


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Export PNG weirdness

2006-08-09 Thread Dar Scott


On Aug 9, 2006, at 9:36 AM, Unhappy Chris Carroll-Davis wrote:


weep, weep.

It's the font.:-(

I haven't worked out what the specific issues are, but it simply  
fails with many, many fonts.


Do you mean that any of many fonts will cause the problem?  Or that  
having many fonts (probably those of some characteristic) in the  
field will cause the problem?


Don't know whether it is a problem with Postscript, TrueType,  
Unicode or what.


I suppose I should lodge this as a bug - quite serious, in my  
opinion - since the ability to output images from specific controls  
was one of the features of 2.7.2 I believe.  I've never used  
bugzilla before(!) is it simple to do?


There is a tiny bit of a learning curve and you have to register.  It  
has been a long time since I registered or had to navigate to  
Revolution Bugzilla.  I jump to a query page with my bookmark and my  
login seems to be automatic.


You can also use a stack available from Ken Ray of Son of Thunder  
Software.


I hope you do report this bug.  The more you can narrow it down, the  
better the response.  You will be able to add details to your report,  
so you can report now and add detail as you get it.  On the other  
hand, maybe just lots of fonts will cause a programmer to cry Arg,  
I knew I shouldn't have limited it to 10!


I can't think of a simple workaround.  Maybe you can temporarily have  
only those displayed lines in the field if the number of lines are  
much greater than what can be displayed and only a few fonts are  
actually displayed in that small of a space.


What OS?

Dar Scott

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: export PNG weirdness

2006-06-29 Thread David Glasgow
And while we are at it, I discovered that pre 2.7, (but I don't know 
which version) exported some PNGs that were *enormous*.  Simple 
screenshots were over 1 meg.  I realised that exporting seemed  s l o w 
but hadn't noticed the file sizes.  It wasn't until I was having a 
clear-out that I found hundreds of monster screenshots lurking on my 
disk.  They seemed OK in terms of displaying, but what was going on, I 
have no idea.


I would imagine it would be quite a challenge to add so much stuff to 
an image without corrupting it completely - unless it was some weird 
parallel universe anti matter anti compression algorithm collision.  
Somewhere out there my doppelganger is scratching his head wondering 
why his PNGs are so absurdly *small*.  Oh dear.  This flight of fantasy 
doesn't bode well for my productivity today.



Best Wishes,

David Glasgow
Carlton Glasgow Partnership

http://www.i-psych.co.uk
On 28 Jun 2006, at 7:59 pm, Chipp Walters wrote:


Hi Chris,

I too, have found some text rendering issues in the 2.7 series. Pre-
2.7, if the image had under a certain number of colors in it, the PNG
export would choose to export in 8-bit-- very disconcerting.

-Chipp



___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: export PNG weirdness

2006-06-28 Thread Chipp Walters

Hi Chris,

I too, have found some text rendering issues in the 2.7 series. Pre-
2.7, if the image had under a certain number of colors in it, the PNG
export would choose to export in 8-bit-- very disconcerting.

-Chipp
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


export PNG weirdness

2006-06-27 Thread Chris Carroll-Davis

Hello all.

I want to output a transparent PNG of formatted text in a field.   
Fine. I use the following script that acts on a non-opaque field:


on mouseUp
  put /Users/chris/Desktop/transtext.png into fPath
  export snapshot from field transText to file fPath as PNG
end mouseUp

Works fine if just roman text is used in field.  Makes a lovely RGB  
png with black text on a transparent background.


However... if I type in some Japanese text into the field, I get  
square black blobs instead of Japanese characters.   If I set the  
opaque of the field to true the text renders correctly but on a solid  
background - which, naturally, I don't want...  Interestingly, if the  
field contains just Japanese, the resulting png seems to be generated  
as an 8-bit indexed colour image.


Can anyone shed any light on this?  I guess there is some issue with  
the way Rev renders unicode(?) in a field.



Chris
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: export PNG weirdness

2006-06-27 Thread David Glasgow
Hey!  I bumped into this earlier today.  I had some fields that had 
exported to PNG fine under 2.2, but one or two went really blocky under 
2.7.2.  I compared their properties, and found that the yucky ones were 
transparent.  The font was Verdana, so it doesn't look like a unicode 
thing.  I can live with opaque buttons in this app, so didn't bother me 
too much


Best Wishes,

David Glasgow
Carlton Glasgow Partnership

http://www.i-psych.co.uk.
On 27 Jun 2006, at 1:09 pm, Chris Carroll-Davis wrote:

However... if I type in some Japanese text into the field, I get 
square black blobs instead of Japanese characters.   If I set the 
opaque of the field to true the text renders correctly but on a solid 
background - which, naturally, I don't want...  Interestingly, if the 
field contains just Japanese, the resulting png seems to be generated 
as an 8-bit indexed colour image.



___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution