Hmmm. Does not seem to be doing it.
Unfortunately, I'm out of ideas; these were mainly off the top of
my head. Without seeing your specific source code, I can't offer
any more suggestions -- it is quite possible something else is
wrong (ie: the identifier isn't set). You probably want
One other thing I'm not sure I understand -
Are you calling setAutosaveName: yourself? Set it to nil in the nib.
Then, call it yourself.
Why can't this be set in the nib? I would have thought this is the
logical place to set it, and that once set any changes to the table
would be
More observations on this -
Unfortunately, I'm out of ideas; these were mainly off the top of
my head. Without seeing your specific source code, I can't offer
any more suggestions -- it is quite possible something else is
wrong (ie: the identifier isn't set).
The identifier is
I'm working on an application that will allow users to add columns of
descriptive information to an NSTableView - the available columns are
determined at launch time by loading a dictionary.
In my test app, I can add columns to my table no problem. Now I am
trying to decide on a robust
If you add all the columns (and remove old ones) before calling
setAutosaveName:, or setAutosaveTableColumns:, then it should work out
okay; it will restore all of the widths, positions, etc.
corbin
On Aug 4, 2008, at 2:03 PM, Rick Hoge wrote:
I'm working on an application that will
Thanks for the suggestion -
I tried calling setAutosaveTableColumns: after adding a column from
code, but on next launch it only showed the columns that are defined
in the nib with IB.
Rick
On 4-Aug-08, at 5:39 PM, Corbin Dunn wrote:
If you add all the columns (and remove old ones)
Are you calling setAutosaveName: yourself? Set it to nil in the nib.
Then, call it yourself. Before you call it, print out all the table
columns to see what they are. Then, load your tablecolumns that you
want (add new ones). Then call setAutosaveName:something. Change the
width of a
Hmmm. Does not seem to be doing it.
I set autoSaveFileName to nil in the nib file, then do the following
in my code:
1) add the new table columns (addTableColumn: etc.)
2) call setAutosaveName:@someFile , call setAutosaveTableColumns:YES
3) manually change width of table column in UI
On Aug 4, 2008, at 4:32 PM, Rick Hoge wrote:
Hmmm. Does not seem to be doing it.
Unfortunately, I'm out of ideas; these were mainly off the top of my
head. Without seeing your specific source code, I can't offer any more
suggestions -- it is quite possible something else is wrong (ie:
Hmmm. Does not seem to be doing it.
Unfortunately, I'm out of ideas; these were mainly off the top of my
head. Without seeing your specific source code, I can't offer any
more suggestions -- it is quite possible something else is wrong
(ie: the identifier isn't set). You probably want
Also, let me step back for a moment and recommend another approach.
Ideally, if you know all possible permutations of the columns that the
user could ever want, then just add them all at design time in the
nib, and hide (setHidden:YES) the ones you initially want hidden.
Then, add a pop on
Also, let me step back for a moment and recommend another approach.
Ideally, if you know all possible permutations of the columns that
the user could ever want, then just add them all at design time in
the nib, and hide (setHidden:YES) the ones you initially want
hidden. Then, add a pop
12 matches
Mail list logo
