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
Support
Electronic Program Guide
WebEPG
Template "start" and "end" comparisons
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="Khurram" data-source="post: 375615" data-attributes="member: 74579"><p>After going through the code, I have found that the template "start" string is searched without any case conversions, but the template "end" string is searched differently based on the following 2 conditions:</p><p></p><p>1) The page source is converted to lower case before the comparison.</p><p>2) The comparison starts from the location of the "start" string.</p><p></p><p>Also, the final part of the string (this is the part which is matched against the actual template) that is obtained from the page source includes the "start" string but not the "end" string.</p><p></p><p>A consequence of (1) is that if your "end" string contains uppercase characters, it will never be matched. That was the problem I was having in another thread. I dont mean to belittle the efforts of James and other developers, but it makes more sense to me to do case insensitive comparisons for both "start" and "end" strings. So I have changed the code to convert both the page source, "start" and "end" strings to lowercase before the comparison.</p></blockquote><p></p>
[QUOTE="Khurram, post: 375615, member: 74579"] After going through the code, I have found that the template "start" string is searched without any case conversions, but the template "end" string is searched differently based on the following 2 conditions: 1) The page source is converted to lower case before the comparison. 2) The comparison starts from the location of the "start" string. Also, the final part of the string (this is the part which is matched against the actual template) that is obtained from the page source includes the "start" string but not the "end" string. A consequence of (1) is that if your "end" string contains uppercase characters, it will never be matched. That was the problem I was having in another thread. I dont mean to belittle the efforts of James and other developers, but it makes more sense to me to do case insensitive comparisons for both "start" and "end" strings. So I have changed the code to convert both the page source, "start" and "end" strings to lowercase before the comparison. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Electronic Program Guide
WebEPG
Template "start" and "end" comparisons
Contact us
RSS
Top
Bottom