From marco.piovanelli at pobox.com Tue Apr 3 08:19:23 2007 From: marco.piovanelli at pobox.com (Marco Piovanelli) Date: Tue, 3 Apr 2007 14:19:23 +0200 Subject: [WASTE-list] Exception in WE3_ATSULayout::MoveCursor In-Reply-To: References: Message-ID: <20070403121923.1230979667@relay.pair.com> On Tue, 27 Mar 2007 13:54:28 -0500, Chinh Nguyen (cnguyen at stata.com) wrote: >FYI, pressing the right cursor key when there is no text results in: > >Exception thrown in function UniCharArrayOffset >WE3_ATSULayout::MoveCursor(UniCharArrayOffset, >ATSUCursorMovementType, WE3_CursorMovementVerb) (WE3_ATSULayout.cp, >line 776); error code = -8801 This was harmless, but I fixed it anyway. The fix will appear in version 3.0.2. >being outputted. It doesn't show in the console log... only XCode's >Run Log. I noticed it in my code first then confirmed it happens in >the WASTE demo too. Exception messages are printed with a vanilla printf to stdout, wherever that happens to be redirected to. Since these messages are meant for debugging, and aren't much useful to end users, they will be silenced in the next release, unless the environment variable "WASTE_DEBUG" is defined. -- marco -- It's not the data universe only, it's human conversation. They want to turn it into a one-way flow that they have entirely monetized. I look at the collective human mind as a kind of ecosystem. They want to clear cut it. They want to go into the rainforest of human thought and mow the thing down. From manistyman at yahoo.com Wed Apr 25 11:42:59 2007 From: manistyman at yahoo.com (Richard Laws) Date: Wed, 25 Apr 2007 08:42:59 -0700 (PDT) Subject: [WASTE-list] WEDisposeView Message-ID: <683580.98836.qm@web60213.mail.yahoo.com> Hello: Am I right in assuming that WEDisposeView() disposes of the WEReference previously passed in to WENewView()? I'm also wondering if there's any substantive advantage to using WEViewReference at the moment. Many thanks. Richard __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From marco.piovanelli at pobox.com Wed Apr 25 13:45:47 2007 From: marco.piovanelli at pobox.com (Marco Piovanelli) Date: Wed, 25 Apr 2007 19:45:47 +0200 Subject: [WASTE-list] WEDisposeView In-Reply-To: <683580.98836.qm@web60213.mail.yahoo.com> References: <683580.98836.qm@web60213.mail.yahoo.com> Message-ID: <20070425174547.469333594@relay.pair.com> On Wed, 25 Apr 2007 08:42:59 -0700, Richard Laws (manistyman at yahoo.com) wrote: >Hello: > >Am I right in assuming that WEDisposeView() disposes >of the WEReference previously passed in to >WENewView()? WEDisposeView disposes (or more exactly, it decrements the reference count) of a WEViewReference that may have been created by WENewView() or WENewViewWithCGContext(). OTOH, a WEReference (a reference to a controller object) can only be released by WEDispose(). A controller (WEReference) may have zero, one or more views (WEViewReferences) attached to it. Views can be bound to either a Quickdraw port or a Core Graphics context. There are three ways to create a view: 1. A view is implicitly created by WENew() when its controller is created, unless you pass NULL in the destRect/viewRect parameters. This view is always QD-bound. 2. WENewView() creates a new QD-bound view and attaches it to the specified controller. 3. WENewViewWithCGContext() creates a new CG-bound view and attaches it to the specified controller. >I'm also wondering if there's any substantive advantage >to using WEViewReference at the moment. It depends on your needs. If you have a single-view controller in an application that still uses Quickdraw, you don't need to know about views. You just manipulate the controller (WEReference) and the view object will be handled transparently behind the scenes. OTOH, if you need multiple views per controller, or perhaps if you need to draw text into a PDF context, you need the new view APIs. HTH, -- marco -- It's not the data universe only, it's human conversation. They want to turn it into a one-way flow that they have entirely monetized. I look at the collective human mind as a kind of ecosystem. They want to clear cut it. They want to go into the rainforest of human thought and mow the thing down. From manistyman at yahoo.com Wed Apr 25 14:45:11 2007 From: manistyman at yahoo.com (Richard Laws) Date: Wed, 25 Apr 2007 11:45:11 -0700 (PDT) Subject: [WASTE-list] WEDisposeView In-Reply-To: <20070425174547.469333594@relay.pair.com> Message-ID: <524439.24375.qm@web60212.mail.yahoo.com> Thanks, Marco. I'm experimenting, so I made some assumptions about WEViewReference. I did, in fact, create a WEReference with WENew() and void view and dest rects, then loaded it into WENewView() with defined rectangles. I've been accessing the WEReference with WEGetViewOwner(). As I say, it's experimental and works, but perhaps pointless in my case. I'm creating a WASTE text HIViewRef embedded in a scrollable HIViewRef, and the use of the word "view" got me intrigued. There appears to be no way that I can create the WEViewReference with a CGContextRef because of the context passed in with the kEventControlDraw handler. Thanks again for the clarification. Richard --- Marco Piovanelli wrote: > On Wed, 25 Apr 2007 08:42:59 -0700, > Richard Laws (manistyman at yahoo.com) wrote: > > > >Hello: > > > >Am I right in assuming that WEDisposeView() > disposes > >of the WEReference previously passed in to > >WENewView()? > > WEDisposeView disposes (or more exactly, it > decrements the > reference count) of a WEViewReference that may have > been > created by WENewView() or WENewViewWithCGContext(). > > OTOH, a WEReference (a reference to a controller > object) > can only be released by WEDispose(). > > A controller (WEReference) may have zero, one or > more > views (WEViewReferences) attached to it. Views can > be > bound to either a Quickdraw port or a Core Graphics > context. > > There are three ways to create a view: > > 1. A view is implicitly created by WENew() when > its > controller is created, unless you pass NULL > in > the destRect/viewRect parameters. This view > is > always QD-bound. > > 2. WENewView() creates a new QD-bound view and > attaches > it to the specified controller. > > 3. WENewViewWithCGContext() creates a new > CG-bound > view and attaches it to the specified > controller. > > >I'm also wondering if there's any substantive > advantage > >to using WEViewReference at the moment. > > It depends on your needs. If you have a single-view > controller > in an application that still uses Quickdraw, you > don't need to > know about views. You just manipulate the > controller (WEReference) > and the view object will be handled transparently > behind the > scenes. OTOH, if you need multiple views per > controller, or > perhaps if you need to draw text into a PDF context, > you need > the new view APIs. > > HTH, > > > -- marco > > -- > It's not the data universe only, it's human > conversation. > They want to turn it into a one-way flow that they > have entirely > monetized. I look at the collective human mind as a > kind of > ecosystem. They want to clear cut it. They want to > go into the > rainforest of human thought and mow the thing down. > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From manistyman at yahoo.com Sun Apr 29 13:56:56 2007 From: manistyman at yahoo.com (Richard Laws) Date: Sun, 29 Apr 2007 10:56:56 -0700 (PDT) Subject: [WASTE-list] tabs in WASTE 3.0.1 Message-ID: <19041.48467.qm@web60221.mail.yahoo.com> Hello: Are tab alignments and tab leader types unsupported in 3.0.1? TIA Richard __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From marco.piovanelli at pobox.com Sun Apr 29 19:14:24 2007 From: marco.piovanelli at pobox.com (Marco Piovanelli) Date: Mon, 30 Apr 2007 01:14:24 +0200 Subject: [WASTE-list] tabs in WASTE 3.0.1 In-Reply-To: <19041.48467.qm@web60221.mail.yahoo.com> References: <19041.48467.qm@web60221.mail.yahoo.com> Message-ID: <20070429231424.142343946@relay.pair.com> On Sun, 29 Apr 2007 10:56:56 -0700, Richard Laws (manistyman at yahoo.com) wrote: >Hello: > >Are tab alignments and tab leader types unsupported in >3.0.1? Tab leaders are currently ignored for all rendering purposes, but tab alignments work for me. Do they not for you? -- marco -- It's not the data universe only, it's human conversation. They want to turn it into a one-way flow that they have entirely monetized. I look at the collective human mind as a kind of ecosystem. They want to clear cut it. They want to go into the rainforest of human thought and mow the thing down.