HTPCInfo plugin v1.15.0 for MediaPortal 1.3.0 and higher (2 Viewers)

[joz]

I think the last solution would be best, maybe even configurable per element, by a dropdown or checkbox so users can decide what they like most.
Programming wise I would go with something like this (if I were doing it);
We now have a htpcinfo_gauges.xml in an import (at least that's how I skinned it). we can make that import dynamic with a string var, for example if a user chooses the gauges the variable #HTPCInfo_gaugetype (or whatever) will be set to "htpcinfo_gauges.xml" when he chooses the progressbars it will be set to "htpcinfo_progressbars.xml". So finally the skinner can incorporate;
<import>#HTPCInfo_gaugetype</import>.
The problem with this however will probably be that you cannot adjust the gauge type per section(say cpu, mem etc.) but just one of the types.

I'll just wait a bit with the freespace problem and will test again when you're ready for release (or sooner )

 

[Micropolis]

Hi Joz,
due to compatibility issues for existing skin files the solution would be the following:

• actually you have 3 different properties: #HTPCInfo.CPUGauge, #HTPCInfo.MemoryGauge and #HTPCInfo.Disk<digit>Gauge
• in the current version, these properties will be set to image name "htpcinfo_gauge_<percent>.png" (<percent> will be replaced with the number of CPU load, Memory Usage and Disk Usage)
• if you select a type (Gauge/Progress bar) in the configuration dialog (e.g. per radio button), the image name will be set to "htpcinfo_gauge_<percent>.png" or "htpcinfo_progressbar_<percent>.png"

This is the best way and the implementation is not so complicated.
My wish: can you send me the pictures for your progress bar from the last screenshot, thx.

Cheers, Micropolis ;-)

 

[joz]

Hey Micropolis,

the solution you are suggesting is not gonna work with the default progressbar images in most skins.
The progress bar accepts a percentage integer as a label and then automatically repeats one of the sections (depends on how it's called progressbar_mid.png for example, defined by skin). So what you're suggesting will work too but that will mean having an image for each state, that doesn't have to be like that with the progressbar It does with the gauge (ps might want to look @ sysinfo's gauges, it generates the image from C# I think, so no seperate images for each percentage stage)

The images I used in my last screenshot were the default progressbar images of streamedMP. I can ofcourse zip them for you but then it would be nice to atleast ask the skin authors for their permission.

 

[Micropolis]

Hey Joz,
nop, I think in my graphic library I can find others.
Again: Is the described solution a good solution for skinners? Sorry, but I want to have only one xml, where the type (and the required image) is driven by a property (like #HTPCInfo.CPUGauge).

Cheers, Micropolis ;-)

 

[joz]

Well I personally feel that it's no optimal solution cause you are increasing cache size with all those extra, not per se needed, images.
The progressbar should be used what it's made for, not work around it by defining your own image for each percentage.

That's just how I feel, so I would say no to that but others might disagree. The import idea I had I do not feel so strongly about, but I do about using progressbars like they were meant to and not recreate the wheel.

The progressbars are already working for me so there's no need for any extra variables for those progressbars, it just needs a percentage as integer. Besides that every skin has it's own progressbar images and so it would feel more like part of the skin.

What you could do to still have 1 file for gauges and have the user control what kind is displayed (progressbar or gauge) is having couple dummy controls or something (or have the gauges and progressbars have an unique ID) so we have something to work with in the skin with Control.IsVisible(). Or you just turn off the controls that should not be visible, by ID

 

[Micropolis]

Hi Joz,
I understand your point of view, nop. But with your suggested solution you are create some interferences to other plugins or requirements, with this I'm not happy.
Other question: When I take a look into the cache folder of my MediaPortal installation and the contained gfx files, only files from the media directory of a skin is cached, subdirectories are not included. Is this configurable inside MediaPortal?

Cheers, Micropolis ;-)

 

[joz]

I can't see the interference but I'm no MP plugin programmer either so I don't know what I'm talking about I'm kinda stubborn on this bit, how come I have done the progressbars as I wanted them (using type progressbar) now, which works beatifuly, cannot be done? It's already working! Or are you experiencing problems with the part that decides whether a gauge or progressbar should be shown?
Or do you want to be using just one control for both?

If the last one is the case keep in mind skinners will have to leave room for stuff cause the images of the gauges have other dimensions than the images for progressbars, especially in height (which is valuable real estate on wide screen tvsets)

You are correct about caching, subdirs are excluded. There unfortunately is no way around this.

 

[scirocco790]

I get a very strange view of the plugin. I´m using Black Glass 1.4 Skin. The screen is flickerung too. Screenshoot attached...
What can I do?

 

[joz]

That's a skin issue which should be reported to the skin author, not the plugin author. Wrong thread

p.s.
Are you running 8 bit color or something? That screen looks pretty ugly to me.

 

[scirocco790]

No the screenshoot is taken using VNC ... Thats why there are 8 Bit colors.