Re: data formatters (still) unreliable?
Re: data formatters (still) unreliable?
- Subject: Re: data formatters (still) unreliable?
- From: Sam Deane <email@hidden>
- Date: Thu, 11 Jun 2009 08:24:30 +0100
I hesitate to ask, but has any work been done on this area of XCode
in the intervening years? Does anyone have any clues as to how I can
get it to work reliably?
I think I've partly answered my own question, at least to the extent
that I seem to have figured out a workaround.
My problem seems to stem from the fact that my plug-in defines
formatter for wchar_t* in its CustomDataViews.plist file, and I was
trying to make use of this in another plist (called "sicore
types.plist", located in the correct place in my Library folder). I
know that the second plist is in the right place, as other definitions
are showing up fine, but my use of wchar_t in this second plist
doesn't work.
It would seem that if you try to describe a derived type in terms of a
type that a plugin defines, you need to also put your derived
definition into the plugin's CustomDataViews.plist.
To give a concrete example:
My plugin defines wchar_t* like so:
{(char *) formatUnicodeString((long *) $VAR, sizeof($VAR[0]), (int)
$ID)}:s
I am working with lots of code which has a type:
typedef wchar_t C16;
I wanted to be able to describe C16* this like so:
{(wchar_t*) $VAR}:s
This ought to work, but doesn't.
However, if I put the following definition into my plugin's
CustomDataViews.plist for C16*:
{(char *) formatUnicodeString((long *) $VAR, 2, (int) $ID)}:s
I can get it to work.
This is possible because I happen to have built the plugin myself, but
it's somewhat counter-intuitive, and not very useful for everyone else
who might want to use my plugin (which I'd like to distribute).
Am I doing something stupid, or is this really the way it works? I've
opened a bug (6961539) on this issue.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden