[Rawstudio-dev] Re: deleted directories

[oleksandr korneta]

on 06/17/2008 11:45 AM Anders Brander wrote:
> Hi,
> 
> Please discard my last mail, I wasn't paying attention :)
> 
> On Mon, 2008-06-16 at 23:34 -0400, oleksandr korneta wrote:
>>> Can you explain how you are trying to delete a directory?
>> my apologies, perhaps I was not clear enough.
>>
>> Consider the following scenario:
>>
>> 1) imagine a bunch of raws in ~/shooting_session_001/
>> 2) I open the rawstudio, point it to the  ~/shooting_session_001/, 
>> process the pictures, export everything to *.jpeg, quit rawstudio.
>> 3) copy *.jpeg to some other place and delete  ~/shooting_session_001/ 
>> (using third-party file manager, rm -rf or whatever you prefer)  along 
>> with all the  *.raw in it.
>> 4) open rawstudio, click on the "Open" tab on the right panel. Guess 
>> what I see -- the directory tree along with my  ~/shooting_session_001/. 
>> Wait! Didn't I just delet it?
>> 5) Hm... Let me check with external file manager. Nope -- actually, it 
>> is back where it was!
> 
> This will happen when Rawstudio tries to save the settings for the photo
> you have open,

not sure I'm following you here. Every time I open rawstudio it creates 
those deleted directories. There is not photo opened from that path 
(just because the path does not exists anymore) and correspondingly no 
settings to be saved. Why doesn't it check for existence of the 
directory first?

> when you quit Rawstudio between step 3 and 4. This is
> clearly a bug. I'm not sure how easy the fix would be thou.

uhm... maybe something like



if (directory exist) & ($.raw exists)
	then (save settings)
	else (complain "directory not found") do nothing


I remember LightZone always complains about nonexisting directory, since 
  it doesn't start in current directory but always tries to open the 
last one. If the directory has been deleted nothing can be done, so just 
let the user know that rawstudio was looking for it and move on.




-- 
regards,
Oleksandr Korneta

I'm running FC7 x86_64 and FC8 i386 on x86_64 hardware, should this matter.

/The nice thing about standards is that there are so many to choose from./