Mini Display Plugin (1 Viewer)

[sonnybonds]

Hello chemelli,

I dont want to get on your nervs :sorry: but my first question again: Is it possible to avoid the lcd-hype driver and maybe write a direct mini-plugin-driver?

Are all drivers minidisplay uses 3rd-party-drivers? I that is so then maybe it is possible to implement a response-time in minidisplay that specifies how long minidisplay waits for the response of the external driver-thread and if necessary kills and reinitialize the driver.
It is only an idea - I don´t know if or with how much effort this could be implemented. I am only searching for a solution how this annoying bug can be solved or bypassed.

Maybe you already have another idea?

Greetings

Sonny

 

[chemelli]

Is it possible to avoid the lcd-hype driver and maybe write a direct mini-plugin-driver?

I think so, but I won't do the coding myself. Sorry.

Are all drivers minidisplay uses 3rd-party-drivers?

On a level or on another yes, because you need "something" to "speak" with the hardware.

Simone

 

[CKB]

Hi Chemelli

Appreciate you're very busy, but if you don't ask and all that

Is it possible to further filter the MiniDisplay xml by the #CurrentModuleId field ?

e.g. <CurrentModuleId> 9811 </CurrentModuleId> in the same was as <Window> 9811 </Window> works

I'm hoping I can display data unique to the process running, e.g. one display for MovingPictures and another for MyTvSeries, etc - but the window is reported for both as FullScreen_Video

Currently running 1.1.0 alpha



Chris

 

[CKB]

Hi Chemelli

Appreciate you're very busy, but if you don't ask and all that

Is it possible to further filter the MiniDisplay xml by the #CurrentModuleId field ?

e.g. <CurrentModuleId> 9811 </CurrentModuleId> in the same was as <Window> 9811 </Window> works

I'm hoping I can display data unique to the process running, e.g. one display for MovingPictures and another for MyTvSeries, etc - but the window is reported for both as FullScreen_Video

Currently running 1.1.0 alpha



Chris

I've worked it out

<ID>9811</ID>

Chris

 

[taalas]

This just got my attention concerning something that I was wondering about for a while:

I got an iMon LCD and the MiniDisplay is working quite well, although when starting a video the displays shows "fullscreen_video" for a short time. The previous post got me thinking...is this a wanted output or debug information?

 

[CKB]

It's output, and personally it's output I see no need for.

I'm in the process of customising my MiniDisplay configuration to give me the display I want when I want it.

So far I have split my output into sections :

<Idle> (the 'MediaPortal' & 'Time' bit)

<BasicHome> (things that work on the BasicHome screen, like showing which module you have highlighted.) This is the bit I haven't finished yet as I need to complete the output requirements when playing media at this screen

<Music> (music guide & playing music)

<TV> (everything related to 4TR and watching Live TV)

<TV Show> (MP-TVSeries)

<Movies> (Moving Pictures)

<Radio> (4TR Radio)

<DVD> (DVD Player)

<Pictures> (My Pictures)

I wanted the <ID>*</ID> bit so I can show different information between MovingPictures and MP-TVSeries, although will have to accept a generic output when viewing the media on the BasicHome screen (as ID for both is 35, which is BasicHome)

It's really down to your personal preferences what display output you want as to what work you do here

Chris

ps. If it helps, I can post the TV section so you get an idea what I'm on about ?

One thing to bear in mind, MiniDisplay looks down the XML until it locates a valid argument to display - so you can manipulate the sections into an order which suits you - or just delete those you don't want if you're brave enough (and have a copy of the original file to prevent crying later !)

e.g. moving the default PlayingVideo section above the generic display DialogItem would probably stop your FullScreen_Video appearing while doing zero damage to the original XML.

 

[1stdead]

It's output, and personally it's output I see no need for.

I'm in the process of customising my MiniDisplay configuration to give me the display I want when I want it.

So far I have split my output into sections :

<Idle> (the 'MediaPortal' & 'Time' bit)

<BasicHome> (things that work on the BasicHome screen, like showing which module you have highlighted.) This is the bit I haven't finished yet as I need to complete the output requirements when playing media at this screen

<Music> (music guide & playing music)

<TV> (everything related to 4TR and watching Live TV)

<TV Show> (MP-TVSeries)

<Movies> (Moving Pictures)

<Radio> (4TR Radio)

<DVD> (DVD Player)

<Pictures> (My Pictures)

I wanted the <ID>*</ID> bit so I can show different information between MovingPictures and MP-TVSeries, although will have to accept a generic output when viewing the media on the BasicHome screen (as ID for both is 35, which is BasicHome)

It's really down to your personal preferences what display output you want as to what work you do here

Chris

ps. If it helps, I can post the TV section so you get an idea what I'm on about ?

Could you tell me how to do that?

 

[CKB]

Could you tell me how to do that?

Which bit - just the editing part ?

See my post at the top of the previous page on how to use the Property Browser.

I'll upload my work-in-progress MiniDisplay.xml when I get home so you can see examples.

Chris

 

[1stdead]

Could you tell me how to do that?

Which bit - just the editing part ?

See my post at the top of the previous page on how to use the Property Browser.

I'll upload my work-in-progress MiniDisplay.xml when I get home so you can see examples.

Chris

Thanks will see if i can spare some time to play with it.

 

[camoura]

Hello !

I have a Matrix Orbital Serial VFD that I cannot get it to work with MiniDisplay. Model is VK204-25. It is a 4 four line 20 chars VFD display.

Any help would be appreciated.

Thanks!!