FROM : John Stiles
DATE : Fri Jan 18 19:30:18 2008
The plot thickens…
I tried this and found that it works sometimes—depending on where the
save panel is rooted!
Up until now, I have always been doing tests on the desktop, and I am
used to pressing "cmd+shift+D" in the save panel to make it warp to the
desktop (rooting it there). In this mode, even creating a new file did
not work to update the state of the existing, visible files. (A newly
created file does appear, if its name doesn't start with a dot, and its
enabled/disabled state is correct. But the already-visible files do not
change their enabled state, even though it looks like the callback is
being called.)
However…! If I root the save panel elsewhere—for example, by choosing
the hard drive icon from the left side of the save panel and then
manually navigating to the Desktop folder, then things work differently!
Creating a new file in this case/ does/ cause the existing files' state
to be updated. (Unfortunately, telling the window's content view to do
-setNeedsDisplay:YES did not cause the files' state to be updated.)
This seems kind of broken to me. Maybe it's Radar time? Either way,
though, I need to make it work now… I can't wait for 10.6 for this to be
fixed :)
Hamish Allan wrote:
> On Jan 18, 2008 5:21 PM, John Stiles <<email_removed>> wrote:
>
>
>> Thanks for the help… any more ideas?
>>
>
> If Leopard Finder is monitoring the directory for changes using
> kqueue, perhaps creating and removing a .dotfile would work?
>
> Hamish
>
DATE : Fri Jan 18 19:30:18 2008
The plot thickens…
I tried this and found that it works sometimes—depending on where the
save panel is rooted!
Up until now, I have always been doing tests on the desktop, and I am
used to pressing "cmd+shift+D" in the save panel to make it warp to the
desktop (rooting it there). In this mode, even creating a new file did
not work to update the state of the existing, visible files. (A newly
created file does appear, if its name doesn't start with a dot, and its
enabled/disabled state is correct. But the already-visible files do not
change their enabled state, even though it looks like the callback is
being called.)
However…! If I root the save panel elsewhere—for example, by choosing
the hard drive icon from the left side of the save panel and then
manually navigating to the Desktop folder, then things work differently!
Creating a new file in this case/ does/ cause the existing files' state
to be updated. (Unfortunately, telling the window's content view to do
-setNeedsDisplay:YES did not cause the files' state to be updated.)
This seems kind of broken to me. Maybe it's Radar time? Either way,
though, I need to make it work now… I can't wait for 10.6 for this to be
fixed :)
Hamish Allan wrote:
> On Jan 18, 2008 5:21 PM, John Stiles <<email_removed>> wrote:
>
>
>> Thanks for the help… any more ideas?
>>
>
> If Leopard Finder is monitoring the directory for changes using
> kqueue, perhaps creating and removing a .dotfile would work?
>
> Hamish
>






Cocoa mail archive

