On Jun 24, 2010, at 10:07 AM, Mariano Martinez Peck wrote:
>
>
> On Tue, Jun 22, 2010 at 8:17 PM, tgc05 <
[hidden email]> wrote:
> Hi Stef. I would have thought the VM initialize processing could be changed to avoid this problem, but I don't know the details :)
>
>
> Hi Thomas. I cope paste here what I said before:
>
> "More in details, the problem is that when you pass an image, it is interpreted as "SmalltalkImage current getSystemAttribute: 1"
> When you drag a second file (in your case a second image) it is interpreted as source file, not image, and thus the error with the encoding.
> Put a breakpoint in the method startUpAfterLogin if you want to experiment a bit.
>
> At least with this, you know why it was the problem and how to avoid it. Maybe we should raise a better error or even better, if I have already defined an image in the ini file, but I drag another one, override the first one and take the dragged one. I will ask in Pharodev mailing list."
>
> So what I recommend you is to put a breakpoint in startUpAfterLogin and start to play. And let us know what happens.
>
> Thanks
>
> Mariano
>
>
> If the problem cannot be fixed, or if it will take time, it would be good to have the work-around described in the "Pharo By Example" book. That is, to comment out or delete the line "ImageFile=Contents\Resources\Pharo-1.0.image" in Pharo.ini. Without this fix, a new Smalltalker will hit the error as soon as they try to use the PBE.image file.
>
> Image file management is one of those things that I like to get a clear understanding of at an early stage when learning a new dev environment.
>
> --Thomas Costick
> _____________________
>
http://twitter.com/3dbloke
>
http://blog.3dbloke.com
>
>
> On 22 June 2010 17:47, Stéphane Ducasse [via Smalltalk] <[hidden email]> wrote:
> thanks thomas.
> This problem was reported on the squeak-vm mailing-list and there is not much we can do.
> May be I'm wrong.
>
> Stef
>
> On Jun 22, 2010, at 6:38 PM, tgc05 wrote:
>
> >
> > Hi. I just want to let people know that this problem is listed on the Pharo
> > application issues page at
> >
http://code.google.com/p/pharo/issues/detail?id=2374&q=INI%20FILE&colspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty#makechanges
> >
http://code.google.com/p/pharo/issues/detail?id=2374&q=INI%20FILE&colspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty#makechanges
>
> >
> > Issue 2374: Dragging a .image in a Windows VM raises an error
> >
> > Hope this is fixed soon, since it also affects anyone working through the
> > early sections of the "Pharo By Example" book.
> >
> > --Thomas.
> >
> > --
> > View this message in context:
http://forum.world.st/Error-invalid-utf8-input-detected-tp2068483p2264408.html
> > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> >
> > _______________________________________________
> > Pharo-users mailing list
> > [hidden email]
> >
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
>
>
> _______________________________________________
> Pharo-users mailing list
> [hidden email]
>
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
>
>
> View message @
http://forum.world.st/Error-invalid-utf8-input-detected-tp2068483p2264434.html
> To unsubscribe from Re: Error:invalid utf8 input detected., click here.
>
>
>
> View this message in context: Re: Error:invalid utf8 input detected.
>
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-users mailing list
>
[hidden email]
>
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
>
>
> _______________________________________________
> Pharo-users mailing list
>
[hidden email]
>
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
_______________________________________________
Pharo-users mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users