[Paraview] registry file?

Mike Jackson imikejackson at gmail.com
Wed Jun 4 10:18:14 EDT 2008


Ok,
  How about this then.
   Have an "Export Settings" feature along with an "Import Settings".  
The export saves the users settings in the .ini format, which the  
importer can then read. I think this would be a better solution and  
cause less confusion among the various platforms.

   Either that OR Put the ini files in the "appropriate" place for  
each platform, which would probably require MORE work than just  
writing an import/export functionality. I guess I should file a  
feature request at this point.

-- 
Mike Jackson   Senior Research Engineer
Innovative Management & Technology Services


On Jun 4, 2008, at 9:59 AM, Utkarsh Ayachit wrote:

> I think it was so that people can share their settings file. Since  
> the settings has things like server resources etc.
>
> Utkarsh
>
> Berk Geveci wrote:
>> I can't remember the reason (Clint will probably chime in) but there
>> was one. We started using the native format and then we switched.
>> On Wed, Jun 4, 2008 at 8:46 AM, Mike Jackson  
>> <imikejackson at gmail.com> wrote:
>>> Why are you using "iniFormat" and NOT QSettings::NativeFormat? It  
>>> is VERY
>>> un-natural for OS X users to go looking for .config in their home  
>>> directory.
>>> If you use QSettings::NativeFormat each platform will get their own
>>> "correct" usage. One small change and LOTS of people happy.
>>>
>>> Unless of course there is some odd reason why ParaView can not use
>>> QSettings::NativeFormat and _must_ use QSettings::IniFormat?
>>>
>>> --
>>> Mike Jackson   Senior Research Engineer
>>> Innovative Management & Technology Services
>>>
>>>
>>> On Jun 4, 2008, at 7:02 AM, Utkarsh Ayachit wrote:
>>>
>>>> Take a look at:
>>>> http://doc.trolltech.com/4.3/qsettings.html
>>>>
>>>> We use iniFormat settings files in ParaView.
>>>>
>>>> Utkarsh
>>>>
>>>> John Doe wrote:
>>>>> It appears to be in the .config directory.  Shold I file a bug  
>>>>> report
>>>>> to have it moved to a more obvious location, such as perhaps a
>>>>> .Paraview directory?  When was this standard for configuration  
>>>>> files
>>>>> invented?  I wasted an hour trying to find it.
>>>>> Juan
>>>>> On Tue, Jun 3, 2008 at 10:36 PM, John Doe <ufnoise at gmail.com>  
>>>>> wrote:
>>>>>> Where do I find the registry file? Every time I start paraview  
>>>>>> it is
>>>>>> always in the same unusable state as before.  Using the "-dr"  
>>>>>> option
>>>>>> makes the problem go away.
>>>>>>
>>>>>> Thanks,
>>>>>> Juan
>>>>>>
>>>>> _______________________________________________
>>>>> ParaView mailing list
>>>>> ParaView at paraview.org
>>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>> _______________________________________________
>>>> ParaView mailing list
>>>> ParaView at paraview.org
>>>> http://www.paraview.org/mailman/listinfo/paraview
>>> _______________________________________________
>>> ParaView mailing list
>>> ParaView at paraview.org
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>> _______________________________________________
>> ParaView mailing list
>> ParaView at paraview.org
>> http://www.paraview.org/mailman/listinfo/paraview



More information about the ParaView mailing list