Thread: nRoute skin (in progress)

Nemo1,

Would it be possible for you to email me a copy of the nRoute project you are using.

From what I can tell it is some form the original posted by SubaruWRX.

You can send it to obrienj@ec.rr.com

Also, is there any documentation on how to use skinbedder?

Regards,
Jim

Originally Posted by obrienj

Nemo1,

Would it be possible for you to email me a copy of the nRoute project you are using.

From what I can tell it is some form the original posted by SubaruWRX.

You can send it to obrienj@ec.rr.com

Also, is there any documentation on how to use skinbedder?

Regards,
Jim

Sorry, no real documentation other than the readme.txt and the comments in all the ini files.

To use it, run "SKINbedder.exe {skin-name}". ...or, if you just run SKINbedder.exe, it will use the default skin defined in SKINbedder.ini.

To make a skin, you just edit ini files and pngs. When you start up, it will run the Startup= script. When you press a button it will run that buttons script. It doesn't do anything by itself (on a timer, on a window popup, etc.), it only does what it is told to do on startup and in button scripts.

Thanks for the quick response.

Just this morning I found the posts that announce R3-p2 which have some very helpful information. From a preliminary scan this looks like a most helpful package for my needs.

A couple of quick questions:

How does one create/edit png files?

When invoking skinbedder.exe in Exectbl.ini, one follows skinbedder.exe with the name of the skin as you point out. Is that the name of the subdirectory for the app in the skinbedder directory or something else?

Could you give me an example of the commands in Exectbl.ini for two different apps that are enabled via skinbedder and what the skinbedder directory tree looks like?

I'm can't seem to get it setup right.

Finally, for now anyway, I can't for the life of me figure out how to make either winspy or autoit get the class name. Could you shed some light on the process?

Regards,
Jim

You edit PNG's with PhotoShop (or just about any other editor, including MS Paint I think [though that will not allow transparancy]).

In RR, you use command line options with a |. So something like this:
"LOAD;iGFreedom.skin;c:\program files\SKINbedder\SKINbedder.exe|iGFreedom;SKINbedd er - iGFreedom", where iGFreedom is the name a a sub-dir containing a skin, and the skins title is set to SKINbedder - iGFreedom.

Many thanks.

I've tried a number of variations on skinbedder.exe <progname> including actually using <> as shown someplace. I would never have guessed a |.

Probably something for the doc.

But I fully understand after 45 years of programming myself that doc is not a programmers favorite activity.

Again, thanks for the help.

BTW, what is the best forum to ask skinbedder questions?

Regards,
Jim

The | is fully documented in SkinCommands.txt in your RR folder. This is how RR sends command-line options. It has nothing to do with SKINbedder. If you had asked a month ago I would have told you I had no clue as I just recently switched from CF to RR. I'm glad I could help though.

You are posting in the right place... this is the SKINbedder sub-forum!

I created a .png file using Microsoft Visio 2000 Pro. Both MS Picture and Fax viewer and MS/Paint from Win/XP read and display it but when I use it with Skinbedder I get and access violation at 004615e8 in skinbedder.exe tryng to read location 0000000.

I can supply the .png file for a test by someone who can tell me if it is in the correct internal format for skinbedder.

I used Visio since I have it, it produces .png files, and Windows Picture and fax viewer and MS/Paint can display it.

I believe I have all of the .ini files correct but will continue to check.

Regards,
Jim

Sorry, that is a bug with Sb. I have no clue how to fix it though. I use to never have that problem (and neither did anyone else unless they were silent about it), but about 3-months ago when I switched to PhotoShop CS (from PS7), it started happening to me all the time. Even with older .exe's that never had the problem before (???). It also started happening to others, even those still using PhotoShop 7 (???).

Anyway, I have found that if I select all, copy to clipboard, do a file->new, paste it, and then Save-As over the original PNG, it will almost always fix the problem (???). That works for me in PhotoShop CS and in CS2 which I am now using.