<br><br><div><span class="gmail_quote">On 4/5/07, <b class="gmail_sendername">Mike Dransfield</b> <<a href="mailto:mike@blueroot.co.uk">mike@blueroot.co.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Diogo Ferreira wrote:<br>> The current INI plugin seems to fail loading when there isn't a<br>> ~/.compiz dir. Since most users won't have it I believe it makes sense<br>> to mkdir it before trying to mkdir the sub-options directory.
<br>> I would have done it but since you use the get dir function a lot it<br>> would mean changing the structure a little and since it's your plugin<br>> I think you know best how to change it accordingly.<br>
><br><br>Ive been meaning to get some clarification on whether<br>or not I can rely on .compiz existing. When I first wrote<br>the ini plugin, I though I could.<br><br>Its more a global directory so I do not create it, but I can
<br>if its required.<br><br>Should I be creating this directory? OR should it be the<br>responsibility of core to make sure this exists (it is defined<br>there)</blockquote><div><br>You're right, it should be the core I guess, since it's an overall directory and if each plugin which wants to use it needs check for its existence it becomes a big amount of duplicated code. Maybe the core could create it on demand?
<br></div><br></div><br>Diogo