realbasic-plugins
[Top] [All Lists]

Re: CFStrings on Win32

To: REALbasic Plugins <realbasic-plugins at lists dot realsoftware dot com>
Subject: Re: CFStrings on Win32
From: Dave Addey <listmail1 at dsl dot pipex dot com>
Date: Tue, 31 Jan 2006 08:41:36 +0000
Delivered-to: realbasic-plugins at lists dot realsoftware dot com
Thread-index: AcYjekBlfsitbo9tEdqp0QAKldpEygCx+TEz
Thread-topic: CFStrings on Win32
Just thought I'd say, FTR, that I solved this problem, and it was the most
spectacularly embarrassing bug on my part - passing a pointer to the wrong
memory by mistake in another part of the code.  All of the suggestions
worked a treat, and thanks to everyone for the help - it works now!

Dave.

> From: Dave Addey <listmail1 at dsl dot pipex dot com>
> Reply-To: REALbasic Plugins <realbasic-plugins at lists dot realsoftware dot 
> com>
> Date: Fri, 27 Jan 2006 19:45:40 +0000
> To: REALbasic Plugins <realbasic-plugins at lists dot realsoftware dot com>
> Conversation: CFStrings on Win32
> Subject: Re: CFStrings on Win32
> 
> Hi Thomas,
> 
> I agree - it is sounding that way.  All of these values were retrieved just
> before I tried to build the CFString.  And I'm no longer surprised that
> CFStringCreateWithCString is returning null, having found out more about the
> weird data I'm sending to it.
> 
> Perhaps this is caused by the way I am buffering the memory access for my
> class properties (in order to make the memory thread-safe on the Mac, where
> it runs on a background thread).  I'll take that as my next line of attack.
> 
> Thanks to everyone who's been helping out with this, btw - it is *much*
> appreciated!
> 
> Dave.
> 
>> From: Thomas Tempelmann <listuser at tempel dot org>
>> Reply-To: REALbasic Plugins <realbasic-plugins at lists dot realsoftware dot 
>> com>
>> Date: Fri, 27 Jan 2006 20:38:54 +0100
>> To: REALbasic Plugins <realbasic-plugins at lists dot realsoftware dot com>
>> Subject: Re: CFStrings on Win32
>> 
>> Dave Addey wrote:
>> 
>>> but on
>>> Win it is reported as 5316944 (that's an integer, not hex) which I don't
>>> recognise.
>> 
>> That doesn't look like a correct encoding to me.
>> 
>>> I've been finding out more about this string, and it seems as though
>>> FileLocation->Length() returns 0.  The length of the cstring is 19, and then
>>> there's that weird encoding.
>> 
>> this all sounds as if memory got overwritten. Do you check these
>> values right at the time when you try to build the CFstring, or
>> later?
>> _______________________________________________
>> Unsubscribe or switch delivery mode:
>> <http://www.realsoftware.com/support/listmanager/>
>> 
>> Search the archives of this list here:
>> <http://support.realsoftware.com/listarchives/lists.html>
> 
> 
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
> 
> Search the archives of this list here:
> <http://support.realsoftware.com/listarchives/lists.html>


_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>