Re: Cocoa view design considerations
Re: Cocoa view design considerations
- Subject: Re: Cocoa view design considerations
- From: "J.M.Brough" <email@hidden>
- Date: Thu, 19 May 2005 15:30:28 +0100
On 19 May 2005, at 14:42, Mark Munz (DevList) wrote:
Spreadsheets handle drawing differently that a true table. They
support the concept of spilling over to the cell next to it (as
long as it doesn't have a value). This application is usually only
useful in spreadsheets, databases don't normally let you spill data
into other columns.
In the paste, I've written a spreadsheet which essentially had row
objects; each row had to layout how far across each cell's contents
could flow (based on the adjoining cells). Spreadsheets also do
weird things like span across cells (that can be to the left as
well as to the right of the cell with data), centered text could
also flow into the previous cell. In the end, you won't have good
spreadsheet functionality (with today's spreadsheet) if you only
deal with things inside a single cell's borders.
That's essentially what you would need to do. Create a one column
table, then create a subclass of NSCell that lays out the various
columns as you need.
Mark Munz
On May 19, 2005, at 6:36 AM, J.M.Brough wrote:
Yup, I was just about to play with Tim's suggestion about using
setFrame. It's just that I've messed something up in the project or
the 10.4.1 update has done something. It could be my fault. It was
working fine when I left it. I now get this error message:
[Session started at 2005-05-19 15:16:12 +0100.]
2005-05-19 15:16:13.506 DxView[1724] CFLog (0): CFMessagePort:
bootstrap_register(): failed 1103 (0x44f), port = 0x3303, name =
'com.apple.DxView.ServiceProvider'
See /usr/include/servers/bootstrap_defs.h for the error codes.
2005-05-19 15:16:13.564 DxView[1724] CFLog (99):
CFMessagePortCreateLocal(): failed to name Mach port
(com.apple.DxView.ServiceProvider)
2005-05-19 15:16:13.770 DxView[1724] The DocumentType type doesn't
map to any NSDocumentClass.
It's not using the document architecture, it's just a straight cocoa
app. using Obj C. I get 'No Document Could be created' when I run
it. Very strange...Learn something new everyday :)
I don't get it...it was working fine. I loaded up the project, read
the docs on setFrame. I've cleaned/deleted the usual. Crash
Reporter is no help because it isn't crashing! Standard development
options...no optimizations...everything is default about this project.
Anyway, I think you might be right about the one column / custom cell
approach. I've pretty much resigned myself to that.
Cheers,
Jason.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden