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
MediaPortal 1 Talk
Monitor shuts down after 10 minutes of inactivity
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="lkuech" data-source="post: 169265" data-attributes="member: 46526"><p>Yes patricon is right. </p><p></p><p>Your plugin is "classic" process plugin. But you have created it as a normal Window plugin and because of this the menu entry is shown.</p><p></p><p>All you have to do is let your class inherit the IPlugin interface. Then you need you own implementations of the start() and stop() methods (init and deinit is not necessary because they are methods of a window plugin).</p><p></p><p>Bye</p><p>Lars</p></blockquote><p></p>
[QUOTE="lkuech, post: 169265, member: 46526"] Yes patricon is right. Your plugin is "classic" process plugin. But you have created it as a normal Window plugin and because of this the menu entry is shown. All you have to do is let your class inherit the IPlugin interface. Then you need you own implementations of the start() and stop() methods (init and deinit is not necessary because they are methods of a window plugin). Bye Lars [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Monitor shuts down after 10 minutes of inactivity
Contact us
RSS
Top
Bottom
