I'm trying to make a vertical slider with a knob that's 1 pt tall. I
can't quite figure out how to do this without rewriting NSSliderCell.
Overriding -knobThickness and returning a particular thickness doesn't
seem to have any effect on the thickness of the knob. The -
setKnobThickness: meth
I've been reading docs and looking at IconCollection for the last week and I
still can't really figure this out.
Here's the behavior I want to model: pretend I'm making poker dice game. I
have a visual representation of the dice, and I want to select a certain
number of them each round.
Right now
Hi,
No, I want control over how many pages I'm dividing my view into, and
precisely how I divide my image into those pages. I'm writing a function for
someone to print N images from 1 large image, and the user of the function
may want to supply the ratios at which to divide the image (vertically
o
More than likely yes. But I'm not certain you can use the EA framework
to detect such a situation anyway (if someone knows for certain I'm
happy to be wrong here). And in absence of further data as to the
nature of the power source, it would be difficult for a developer to
recognize this si
To Squ:
I read through all your posts today and, although several people have
asked you, I still don't see where you've confirmed that this garbage/
cleanup is indeed a performance issue. My recommendation remains that
you confirm this first, especially now that multithreading Core Data
h
I had this problem once when I had accidentally called
makeKeyAndOrderFront: on the window from a secondary thread. Animated
system controls and tracking rects would work.
On Aug 15, 2009, at 7:45 PM, Thomas Bauer wrote:
Thanks for your response.
I am not quite sure if I understand you co
On Sun, Aug 16, 2009 at 10:35 AM, Squ Aire wrote:
>
> I am not *explicitly* marking anything as garbage. Whenever a user decides
> to remove a ValidKeys managed object, corresponding key-value pairs in all
> the userInfo dictionaries are *conceptually* marked as garbage. This is
> because I do no
Dear list,
After some hours of research I realise that I need some advice on how
to tackle this: My goal is to render a graph [1] consisting of at most
100 nodes and 300 edges (most of the time the graph will be much
smaller, though). I have an algorithm to position the nodes and the
algo
I've been reading docs and looking at IconCollection for the last week and I
still can't really figure this out.
Here's the behavior I want to model: pretend I'm making poker dice game. I
have a visual representation of the dice, and I want to select a certain
number of them each round.
Right now
On 2009 Aug 16, at 17:21, Graham Cox wrote:
I have an outline view using source list style.
When I right-click on the view, the item under the mouse highlights
with a blue outline independent of the current selection. This gives
the impression that the menu command applies to that item, no
On 17/08/2009, at 3:56 AM, Renzil D'Souza wrote:
I'm trying to print a really large image into 'N' pages. So I over-
rode
'knowsPageRange' and 'rectForPage'.
If you're simply trying to tile a large view over 'n' pages, you don't
need to do this - that's what it will do by default with no
I have an outline view using source list style.
When I right-click on the view, the item under the mouse highlights
with a blue outline independent of the current selection. This gives
the impression that the menu command applies to that item, not the
real selected item. In my case my menu
> I mean there is only 1 digit after the decimal. It should not have the range
> problem with a value this small.
Because you're translating from a decimal representation to a binary one,
and back again. Consider a very simple case: 0.1. What sum of powers of two
equals 0.1? (Hint, it's an infinit
On Aug 16, 2009, at 3:02 PM, Graham Cox wrote:
On 17/08/2009, at 1:47 AM, Squ Aire wrote:
Key-value pairs in the userInfo dictionaries are "marked as garbage"
as the app is running and depending on various factors.
Don't "mark as garbage" - delete them. Problem solved. If you need
them to s
On 16 Aug 2009, at 20:46, tim lindner wrote:
Is it possible to add an encoding to CoCoa?
I have some text data from a legacy system which is ASCII for 0-127,
but
128-255 is unique to the system. I'd like to load it into a text view
and "just have it work".
Hi Tim,
It's worth checking whet
Well, certainly one way would be to preprocess the text buffer,
converting the custom characters into a standard encoding like UTF-8,
then passing the processed buffer into +[NSString
stringWithUTF8String:]. At that point it would "just work" since it's
in a known encoding.
Depending on w
Is it possible to add an encoding to CoCoa?
I have some text data from a legacy system which is ASCII for 0-127, but
128-255 is unique to the system. I'd like to load it into a text view
and "just have it work".
What options do I have?
--
tim lindner
tlind...@macmess.org
Hi,
I'm trying to print a really large image into 'N' pages. So I over-rode
'knowsPageRange' and 'rectForPage'. Since I was able to successfully draw on
a single page, my rectForPage function returns the entire 'print view frame'
itself, and I draw a sub-image in this frame. My understanding is th
> Don't "mark as garbage" - delete them. Problem solved. If you need
> them to stick around in the garbage state, they're not garbage!
I am not *explicitly* marking anything as garbage. Whenever a user decides to
remove a ValidKeys managed object, corresponding key-value pairs in all the
user
On 16 Aug 2009, at 17:11, Gideon King wrote:
I have some tests that are working fine in xcode, but I am having
difficulty getting them running in Instruments. Would appreciate
help to sort out the args.
Perhaps xcode-users would be a better list to ask this question on?
Kind regards,
Alas
I have some tests that are working fine in xcode, but I am having
difficulty getting them running in Instruments. Would appreciate help
to sort out the args.
Currently I am using
Executable: /Developer/Tools/otest
Environment: NSZombieEnabled YES
Args: -SenTest Self /whatever/Whatever.octest
On 17/08/2009, at 1:47 AM, Squ Aire wrote:
Key-value pairs in the userInfo dictionaries are "marked as garbage"
as the app is running and depending on various factors.
Don't "mark as garbage" - delete them. Problem solved. If you need
them to stick around in the garbage state, they're not
On Wed, 5 Aug 2009 10:31:35 -0600, David Springer
said:
>Folks,
>
>I recently switched to using an .sdef in my Cocoa app for defining AS event
>handlers. The problem is that suddenly it looks like my app defines the
>property 'points' and this breaks other apps which send AS events to mine.
>
>In
On Aug 16, 2009, at 11:47 AM, Squ Aire wrote:
So, just imagine that I am dealing with this situation, have this
garbage and need to clean it up :)
[ FACE-PALM ]
Unspecific question? Unspecific answer:
Memory Management Using Core Data
http://developer.apple.com/documentation/Cocoa/Conce
> Seems to me that the source of the problem is the mixing of transient
> and persistent key-value pairs within the same dictionary. If you
> store the transient pairs in a dictionary of their own, that whole
> dictionary could be transient.
It's not like that. I don't decide beforehand what is
On Aug 16, 2009, at 11:34 AM, Squ Aire wrote:
For now, just imagine that a set of valid (non-garbage) keys are
stored in a ValidKeys entity (with a single attribute called 'key'
of type string). Or just imagine some global array storing those
keys if you like that better.
...
Surely it
On Aug 16, 2009, at 11:22 AM, Squ Aire wrote:
Just to make it clear: The whole userInfo dictionary will tend to
NOT be "garbage". Only a subset of key-value pairs within the
userInfo dictionaries for the employees will be "garbage". I want to
get rid of this subset without bothering the use
For now, just imagine that a set of valid (non-garbage) keys are stored in a
ValidKeys entity (with a single attribute called 'key' of type string). Or just
imagine some global array storing those keys if you like that better.
Now, imagine that we have chosen a bunch of employees to "clean up"
On Sun, Aug 16, 2009 at 11:22 AM, Squ Aire wrote:
>
> Just to make it clear: The whole userInfo dictionary will tend to NOT be
> "garbage". Only a subset of key-value pairs within the userInfo dictionaries
> for the employees will be "garbage". I want to get rid of this subset without
> botherin
On 17/08/2009, at 1:22 AM, Squ Aire wrote:
Just to make it clear: The whole userInfo dictionary will tend to
NOT be "garbage". Only a subset of key-value pairs within the
userInfo dictionaries for the employees will be "garbage". I want to
get rid of this subset without bothering the user
Thanks for the reply.
Just to make it clear: The whole userInfo dictionary will tend to NOT be
"garbage". Only a subset of key-value pairs within the userInfo dictionaries
for the employees will be "garbage". I want to get rid of this subset without
bothering the user in any way.
Therefore, t
On 2009 Aug 16, at 05:00, Squ Aire wrote:
I really don't want to clean the garbage "on the go/before
persisting" because I don't want to let the user wait unnecessarily.
The purpose of this garbage buildup is the benefit of more
responsive app, at the cost of little more temporary storage.
On Aug 16, 2009, at 8:00 AM, Squ Aire wrote:
I have an Employee entity with the attribute userInfo, which is a
binary data type that stores some NSDictionary of key-value pairs.
Sounds reasonable.
With time, as the user uses the app, "garbage" will pile up (albeit
gradually) in these dic
What is the current best practice to obtain the MobileMe username as
configured in the MobileMe Preference pane? Previously, the
DotMacKit.framework allowed but this is no longer maintained with no
64bit version available. One could search the Keychain for passwords
of Kind ".Mac" but it do
I have an Employee entity with the attribute userInfo, which is a binary data
type that stores some NSDictionary of key-value pairs.
With time, as the user uses the app, "garbage" will pile up (albeit gradually)
in these dictionaries that are associated with the employees. And by "garbage",
I
Cool - haven't used conditional breakpoints before, and didn't realize
about objc_exception_throw...
That gives me completely different information, but much more useful:
#4 0x97578cba in -[NSAtomicStore(_NSInternalMethods)
_insertNodeIntoMainCache:] ()
#5 0x97578c51 in -[NSAtomicStore(_NS
On 16/08/2009, at 9:26 PM, Gideon King wrote:
Any suggestions as to where to look for a solution to this would be
very welcome.
How about setting a conditional breakpoint on [NSDictionary
setObject:forKey] with the condition object == nil?
Also, set a breakpoint on objc_exception_throw
Hi, I'm hoping someone may have encountered something like this
before, or have knowledge of the internals of NSPersistentStore...
I am getting an exception on NSDictionary setObject:forKey: (attempt
to insert nil key), and although I am not getting any stacktrace, it
appears when I step th
On 16/08/2009, at 5:51 AM, Iceberg-Dev wrote:
When the drop is validated in the right window (type of item
accepted), I would like to either display a window above the right
window or change the right window content to give the user a list of
more detailed possible drop locations.
Someth
On Aug 16, 2009, at 2:03 AM, Jerry Krinock wrote:
On 2009 Aug 15, at 12:51, Iceberg-Dev wrote:
When the drop is validated in the right window (type of item
accepted), I would like to either display a window above the right
window or change the right window content to give the user a list
40 matches
Mail list logo
