next »

[tails_]

The reason why is because everyone has a favorite skin and you can use it to make it a new Default skin.

This still does not explain why one will want to integrate skin into his executable.

Can anyone make a section to add to the executable that will get it it work and also tell me what to change the function id's to.

Sounds like "I dunno how to write code, can anyone do that for me so I can add checkbox to which calls it?"

[Dotpitch]

How and, most importantly, why?

The reason why is because everyone has a favorite skin and you can use it to make it a new Default skin.

I have a favourite skin too, and it's the only one I see when I start XMPlay. Why would I want to make it the default skin? And how do I make it the default skin?

I also started a Icon collection in the program itself for the file associations. So if you know of any good, nice, or otherwise neet icons email them to me.

Do you have perm... oh, you probably didn't ask, right. XMPlay file icon set by Cypress is a very nice one.

I know I should fix it. But how the function id for both of them is 0. ... Can anyone make a section to add to the executable that will get it it work and also tell me what to change the function id's to.

Currently, you're the only one modifying XMPlay, so I guess you should fix this yourself. I'd like to see Options and stuff respond to different skins colours, so when will you have that feature working?

[tails_]

Dotpitch
Adding skinning to default Windows' window () is not something to be done with resource editor, so far I see only one possible way: write a program that will receive all Windows' dialog drawing procedures from one of XMPlay threads or whole process, process them and display customized dialog window in some way. Trying to add such code to already existing application is not something average user can do, it's just too hardcore.

[Chinese Sausage]

Adding skinning to default Windows' window.
I see it as unnecessary.

[dbz]

Tails_ I think you're missing Dotpitch's point. PSXGamerPro1 is trying to hack xmplay to do all these other things, and maybe he can do a couple things by hacking it, but the person who the made the program (Ian) can do anything he wants with his program. So why not ask him, when he's willing to hear our suggestions? I know if it was me, I wouldn't want someone messing around with my program without asking me. PSXGamerPro1 is acting like it's his program. Where's the respect? If you want something changed, I suggest you do like the rest of us - ASK.

[PSXGamerPro1]

XMPlay file icon set by Cypress is a very nice one.

I am adding that now.

Tails_ I think you're missing Dotpitch's point. PSXGamerPro1 is trying to hack xmplay to do all these other things, and maybe he can do a couple things by hacking it, but the person who the made the program (Ian) can do anything he wants with his program. So why not ask him, when he's willing to hear our suggestions? I know if it was me, I wouldn't want someone messing around with my program without asking me. PSXGamerPro1 is acting like it's his program. Where's the respect? If you want something changed, I suggest you do like the rest of us - ASK.

What's wrong with adding the function to skin the Dialogs. These problems remain I don't have C++ v6.0, I don't know the code to add this, And I don't know what section to rip the code out of it to add it to XMPlay. In the meantime, enjoy my XM tune for Bejeweled 3 (You or anyone else can help by getting rid of unused samples in the file to make it smaller). Here

[dbz]

I don't think it's wrong that you want to help improve the program, but I think you are going about it the wrong way. I think skinning the options window is a good idea, but it's not up to you to do it. If Ian says "Go ahead and do it", then fine - go for it. But to think you can just do whatever you want with his program, is not ok... and I'm not the only one saying it. I've got nothing more to say on this subject.

[PSXGamerPro1]

Hows this. those checkboxes are useless. And I am not thinking about bitmaps anymore. The way to now skin the dialogs lies in my "skinconfig.txt" modified example. Includes stuff that dont exist or I think don't exist yet.

skinconfig.txt

scaler_lit = ? ? ?
scaler_pressed = ? ? ?
scaler_search = ? ? ?
scaler_title = ? ? ?

color_main = ??????
color_title = ??????
color_text = ??????
color_info = ??????
color_help = ??????
color_helpback = ??????
color_listtime = ??????
color_listdead = ??????
color_listmark = ??????
color_listhover = ??????
color_infoback = ??????
color_seethru = ??????
color_search = ??????
color_volume = ??????
color_volumeup = ??????
color_volumebown = ??????
<!-- The folowing is the functions that I would like named this for skinning the dialogs.
color_dialog_back = ??????          ; This colors the back (does not color the editboxes).
color_dialog_edit_back = ??????       ; This colors the back of the editboxes. Also works on dropdown menus before you click on them.
color_dialog_edit = ??????          ; This colors the border of the editboxes.
color_dialod_text = ??????          ; This colors the text of the dialogs.
color_dialog_buttons = ??????          ; This colors the buttons.
color_dialog_checkboxes = ??????       ; This colors the checkboxes.
color_dialog_dropdown_menus = ??????       ; This colors all the dropdown menus that pops up after you click on them.
color_dialog_border = ??????          ; This colors the borders of all dialogs that do have borders. Dialogs that don't have them are not affected. Useful for most of the dialogs.
color_dialog_un4seen_logo = ??????       ; This colorizes the "un4seen logo" in the "Options and stuff" window.
color_dialog_scroolbar = ??????          ; This colorizes any scroolbars in any of the dialogs.
-->

pos_left = ? ?
pos_right = ? ?
pos_litleft = ? ?
pos_litinfo = ? ?
pos_scrollinfo = ?
pos_listnum = ?
pos_infoframe = ?

font_title = ?
font_titlesize = ?
font_time = ?
font_timesize = ?
font_main = ?
font_mainsize = ?
font_help = ?
font_helpsize = ?
font_list = ?
font_listsize = ?
font_listnum = ?
font_listnumsize = ?
font_info = ?
font_infosize = ?

text_author = ?
text_url = ?

[tails_]

dbz
True, I don't even remember why I started reply instead of just posting.

Geez, just don't understand why someone might want colored/skinned options window so badly, it's not like you see it often.

[Dotpitch]

These problems remain I don't have C++ v6.0, I don't know the code to add this, And I don't know what section to rip the code out of it to add it to XMPlay.

Hows this. those checkboxes are useless.

Oh really? So you can't add any new features at all? Well, that certainly lowers the usefulness of this mod.

Could you at least tell us how to change the default skin and why one would like to change the default skin? And remember, answering 'because everybody has a favourite skin' is not good enough for me .

[saga]

These problems remain I don't have C++ v6.0, I don't know the code to add this

I don't know how you imagine that computers and compilers work, but VC6 won't enable you to magically modify the original XMPlay sourcecode that you don't have.

[PSXGamerPro1]

These problems remain I don't have C++ v6.0, I don't know the code to add this

Found it, It is the Pro edition and it's VC++ 6.0. That problem is gone if it works fine with the code. Then I would not have to convert the project with VC++ 2010.I have an error when opening VC++ 6.0 Pro.
Any way to fix this?