home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Quality Assurance
Bugreports
Archive
Redirected log path: some files created in standard path
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="HTPCSourcer" data-source="post: 1149561" data-attributes="member: 74879"><p>Hi [USER=83973]@Owlsroost[/USER] ,</p><p></p><p>I do appreciate your efforts <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" />.</p><p></p><p>However, I don't think that it is a good idea to start a development where directory path information would begin to be scattered throughout the registry and needs to be maintained manually. Also your versions would need to become part of the official builds. Anayway, unless we cannot harmonize everything to correctly use the information as per the mediaportaldirs.xml, my personal view would be to keep things as they are now rather than promoting this possibility.</p><p></p><p>Actually, the symbolic link possibilities would be as good as the mediaportaldirs.xml, wouldn't they? So why actually bothering about mediaportaldirs when a simple batch script could do the job? Or am I missing something?</p></blockquote><p></p>
[QUOTE="HTPCSourcer, post: 1149561, member: 74879"] Hi [USER=83973]@Owlsroost[/USER] , I do appreciate your efforts :). However, I don't think that it is a good idea to start a development where directory path information would begin to be scattered throughout the registry and needs to be maintained manually. Also your versions would need to become part of the official builds. Anayway, unless we cannot harmonize everything to correctly use the information as per the mediaportaldirs.xml, my personal view would be to keep things as they are now rather than promoting this possibility. Actually, the symbolic link possibilities would be as good as the mediaportaldirs.xml, wouldn't they? So why actually bothering about mediaportaldirs when a simple batch script could do the job? Or am I missing something? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Quality Assurance
Bugreports
Archive
Redirected log path: some files created in standard path
Contact us
RSS
Top
Bottom