Am Sat, 21 Feb 2009 09:28:47 -0600 (CST)
schrieb "Gabriel M. Beddingfield" <[email protected]>:

> Looks like the solution is to make sure that the default
> ~/.hydrogen/hydrogen.conf always has something like:
> 
>     <patternCategories>
>         <categories>not_categorized</categories>
>     </patternCategories>
> 
> Or else, find a better way to handle the default:
> 
>     <patternCategories />
> 
> Peace,
> Gabriel
> 
 oh yes,
if i implement this categories feature, i forgot to add this lines into the 
default config file. 
maybe we can put some more categories into the conf file. i arrange, that user 
will see her categories into the categories combo box in pattern preferences 
dialog. if users create a new category this will create a new entry un h2 conf 
file.

I don't implement a pattern category seek. maybe you have some patterns inside 
your data/patterns directory but you use a brand new h2.conf file the existing 
pattern categories will not restore into config file.  



e.g. some default categories for h2 config file
     <patternCategories>
         <categories>not_categorized</categories>
         <categories>punk</categories>
         <categories>garage</categories>
         <categories>noise</categories>
         <categories>jazz</categories>

or more arrangement categories 

         <categories>fills</categories>
         <categories>verse</categories>
         <categories>breaks</categories>
     </patternCategories>

i don't know

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Hydrogen-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel

Reply via email to