Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: Changes I'd Like to See in Community-SD OSD Skin

  1. #11
    Join Date
    Oct 2007
    Location
    Southern California, US
    Posts
    769
    Quote Originally Posted by johnsonx42 View Post
    Your screenshots just look wrong to me. Everything appears oddly out of place, and covers nearly the entire screen.

    Don't get me wrong, I do understand why the change is desirable for those who use the various zoom functions of their TV's.
    You should consider that the screen caps I provided with the original post were of a letterboxed program shown in a 4:3 format. If the show is not letterboxed then there is more program image at the top and bottom and the OSD covers less of the total image.

  2. #12
    Join Date
    Sep 2008
    Location
    California
    Posts
    5,587
    Quote Originally Posted by LewE View Post
    You should consider that the screen caps I provided with the original post were of a letterboxed program shown in a 4:3 format. If the show is not letterboxed then there is more program image at the top and bottom and the OSD covers less of the total image.
    Yes, but it covers most of the MIDDLE of the image.

    No point in trying to convince me anyway, I already volunteered to implement the change as an option.
    NPVR Tech Support Sticky - - http://forums.gbpvr.com/showthread.p...612#post473612
    ---------------------------
    my config: NPVR 3.2.9/Win7Pro/Athlon II X3-440/radeon hd4550/hvr-2250/hvr-850/KWorld 315U/TimeWarner QAM & Analog, OTA ATSC/schedules direct

  3. #13
    Join Date
    Oct 2007
    Location
    Southern California, US
    Posts
    769
    Quote Originally Posted by johnsonx42 View Post
    Yes, but it covers most of the MIDDLE of the image.

    No point in trying to convince me anyway, I already volunteered to implement the change as an option.
    I got to thinking and I have another suggestion. I'll keep trying until I get it right.

    In some skin files (e.g. TV Listing) there are comments about what the parameters control. Others, like OSD skin, do not have them.

    Many of the comands in a skin file are things that users would not change unless they want to try completely different looks for the plug-ins. I am not concerned about these items. Someone who plays with these parameters falls into a completely different group of users than I am trying to address. Those are the people who might want to tweak small things like font size or color, etc.

    My "solution" is to add commments in skin files to the parameters that this second group of users might be most likely to modify. Before each such command in the skin file, add a comment like
    <!-- COMMONLY CHANGED ITEM-->
    with a description of what the parameter controls in terms that descriptive to the new user.

    For example, in the OSD skin there are four timeline related parameters:

    TimeLineNotAvailable
    TimeLineAvailable
    TimeLineAvailableAD
    TimeLineNotYetAvailable


    I suspected I wanted to change one of them but had to go trial and error with each to find which one I wanted.

    I think that, at the least, adding the "commonly changed item" comment would help a lot of us users who like to make small changes to the skins. It would help us find those parameters that we might be interested in.

    I still think some changes, such as coloring the timeline to indicate whether autoskip is in effect should be added to the basic skin. Others that might be less desired by all the users, such as repositioning the VideoShowInfo, should at least have the "commonly changed item" comment and a description about exactly what VideoShowInfo is.

    If there is agreement about this kind of commenting, I think it should be a "standard" for all skin files; not just the one we are discussing now.
    Last edited by LewE; 2009-10-26 at 07:34 PM.

  4. #14
    Join Date
    Nov 2005
    Location
    Michigan, USA
    Posts
    3,526
    Quote Originally Posted by johnsonx42 View Post
    Yes, but it covers most of the MIDDLE of the image.

    No point in trying to convince me anyway, I already volunteered to implement the change as an option.
    Are you making this change? I am looking on an update coming out the weekend of Nov 21.
    Fatman_do

    HTPC: AMD XP+2500, 512MB DDR (400) ~ Capture Device: Hauppage PVR-150
    Storage: 30GB OS & Recording, 160GB Post Processing & Archive
    Video Output: HD 32" TV via eVGA Geforce 6200le 256MB AGP DVI-HDMI cable out
    Audio Output: Turtle Beach Riviera S/PDIF Optic Output (Digital pass thru only) to Home Theater Receiver



    Moderator | Tutorials | Community Skin | CommunitySkin-SVN

  5. #15
    Join Date
    Nov 2005
    Location
    Michigan, USA
    Posts
    3,526
    I didn't include anything here in the latest installer, did not know what direction to go so I am open to suggestions here.
    Fatman_do

    HTPC: AMD XP+2500, 512MB DDR (400) ~ Capture Device: Hauppage PVR-150
    Storage: 30GB OS & Recording, 160GB Post Processing & Archive
    Video Output: HD 32" TV via eVGA Geforce 6200le 256MB AGP DVI-HDMI cable out
    Audio Output: Turtle Beach Riviera S/PDIF Optic Output (Digital pass thru only) to Home Theater Receiver



    Moderator | Tutorials | Community Skin | CommunitySkin-SVN

  6. #16
    Join Date
    Sep 2008
    Location
    California
    Posts
    5,587
    ah, sorry, have been super busy with other things lately, haven't even been on the forums here but once every few days....

    I will look at this today or tomorrow, I had an idea as to exactly how I was going to do that, now I just have to remember what it was.
    NPVR Tech Support Sticky - - http://forums.gbpvr.com/showthread.p...612#post473612
    ---------------------------
    my config: NPVR 3.2.9/Win7Pro/Athlon II X3-440/radeon hd4550/hvr-2250/hvr-850/KWorld 315U/TimeWarner QAM & Analog, OTA ATSC/schedules direct

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •