Imagesource of char not working as expected in Windows

Jim Ault jimaultwins at
Tue Dec 29 13:38:50 EST 2009

My rule about paths on any system...
  -1- avoid spaces in path names
  -2- avoid dates in file and folder names, such as "hearth jpgs  
An operating system can allow characters because it knows the  
difference between literal name characters and the control characters.

  -3- When accessing files and folders, do a test before using data to  
be sure the path exists, has correct permissions, etc.

such as

   if there is a folder "holidayFunPictures/"
   if there is a file "holidayFunShots/kids/snowFight.jpg"

put binfile:a.png" into tempVariable
if tempVariable is not empty then
    --we have data

If your solution ever gets to the point of including shell commands,  
this adds another level testing to be sure of valid data processing. A  
standalone should always assume the users computer could have changes  
that prohibit access, such as user account changes and authorizations,  
operating system reinstalls, etc.

Hope this helps

Jim Ault
Las Vegas

On Dec 29, 2009, at 10:09 AM, Mike Bonner wrote:

> Based on your test it looks like the comment about "vanilla  
> characters" is
> probably correct.  It works when using a string with no spaces for the
> directory.  When you setup your string you used   put "C:\Documents  
> and
> Settings\zhangt\Desktop\imgFolder" into k
> For the real directory you wish to use change it to this.
>  put quote & "C:\Documents and Settings\zhangt\Desktop\directory with
> spaces\ another with spaces" & quote into k
>> The following script works in a standalone created on Windows XP and
>> running on Windows XP.
>> on mouseUp
>>  put "~" after fld "aFld"
>>  put "C:\Documents and Settings\zhangt\Desktop\imgFolder" into k
>>  set the defaultFolder to k
>>  set the imageSource of last char of fld "aFld" to "binfile:a.png"
>> end mouseUp
>> Perhaps something gets undone when the script travels through the  
>> wormhole
>> from the Mac universe to the Windows universe. Does Dr. Who  
>> frequent this
>> forum?

More information about the Use-livecode mailing list