| Main > Software Forum |
| Johnny 5 and LedWiz |
| << < (12/22) > >> |
| RandyT:
Ok, worked this time. Here's something you may find interesting (I did.) It appears that Windows (2K at least) will automatically register an OCX if it is in the same folder as the executable that uses it and that executable is run. After I ran any program that made use of the OCX, with it present in the same folder, it was ready to use by any program on the system that required it. To make the OCX inaccessible again, I had to use regsvr's /u function and feed it the path to the OCX file that was first found by the system. BTW, the color picker is pretty cool. But if one were going to add a color picker to a utility, I would suggest the ability for the user to "offset" each of the 3 primary colors by a set value to account for variations in RGB LED's. Probably a "White-point" setting that is carried through the rest (I know this is just a start, it's just a suggestion in case you, or others haven't considered it.) RandyT |
| horseboy:
--- Quote from: MYX on August 10, 2006, 10:33:53 am --- I am not a programmer so please forgive the naivity of the following questions. I pick things up pretty darned fast, but alot goes right over my head. Ok, I do not know where MAME stops and the FE begins. I would love to see the extras that PM offers available in the FE world if the MAME side is too hard to keep up with. But again I do not know what the limits of the FE are. I am a GGG user for interfaces, lighting, and joys, so obviously I sit in the GGG camp and will cheer on the guy who is making progress happen. The 2 majors for me are the LEDwiz functionality and the auto DRS selection per game. --- End quote --- Howard's FE is Dragon King, and it has nothing to do with the project at hand. This project has to do with adding LedWiz support to Johnny 5. J5 is an external app used to view the controls of a particular game. Basically it shows the layout of your cp with each button labeled with its corresponding action. Some poeple use it to show the buttons on screen before the game loads. Others have set it up show up when the game is paused. Howard is also working on dual screen functionality so that it can be displayed at all times on a second display (ie. PSone screen). So, when I figured out PowerMame was dead, I wanted a LedWiz solution that could be used with any version of mame (and possibly other emulators). Since J5 knew what buttons were used in a game, I thought (having no programming skills, pretty much just hoping) that it would be relatively easy to implement LedWiz support into J5. I started this thread to see what Howard thought. He thought it was a good idea, and here we are... On a side note Youki has just received a LedWiz and is planning on implementing functionality into AtomicFE, so you may want to ask him what he plans on doing with it. |
| Howard_Casto:
Just to clarify... I might... keyword might add ledwiz support to dk in the future. The thing is I'm not sure what a fe has to do with cp lights. I suppose I could have lights to go with skins, but right now it seems too much form and not enough function for my tastes. However, as Aaron Giles seems to be on the output bandwagon (read the qbert thread in this forum) powrmame might not be needed anymore. It looks like we might finally get proper outputs in mame, meaning any crappy old third-party app can set lights and stuff based on real-game outputs. I am working on such an app as well, but I'm not going to bother starting until the mame stuff is worked out. Sirp has a utility he made that'll do the 49 way stuff. You can find it over at fe.donkeyfly.com in the idvt forum. Randy: Yeah the color picker isn't calibrated yet. I haven't started on that part because it'll be frikkin hard to implement. It'll probably involve me taking the sliders to certain points and looking at the real world results on some ice buttons. Yeah I found out about the ocx thing too while I was trying to figure out why the heck the thing was working without a ocx. The dropping it in the folder thing always worked, even on 98.... the thing about registering the ocx automatically kinda threw me for a loop. I'm not sure why it is done this way, seems to cause more problems than the old method. It explains why some applications seemingly don't need the components though. I've downloaded so many examples over the years the ocx's a random program might need are probably already on my drive somewhere. |
| RandyT:
--- Quote from: Howard_Casto on August 10, 2006, 02:28:03 pm ---Sirp has a utility he made that'll do the 49 way stuff. You can find it over at fe.donkeyfly.com in the idvt forum. --- End quote --- BTW, I think the ActiveX control is going to include GP-Wiz49 switching capabilities in the next rev. Might as well have one tool that does it all. --- Quote ---Yeah I found out about the ocx thing too while I was trying to figure out why the heck the thing was working without a ocx. The dropping it in the folder thing always worked, even on 98.... the thing about registering the ocx automatically kinda threw me for a loop. I'm not sure why it is done this way, seems to cause more problems than the old method. It explains why some applications seemingly don't need the components though. I've downloaded so many examples over the years the ocx's a random program might need are probably already on my drive somewhere. --- End quote --- Hehe, you must have forgotten about it then. That was one of the things (the ability to drop it in the same folder as the app) you just said you disliked about an OCX compared to a DLL :) I've been told that an OCX is really just a more advanced DLL. This is probably part of what makes it "more advanced". It only makes sense to make the OCX available to the entire system once it is used by an application that requires it. Just the OS thinking for the user again, I guess. In this case, I think it's a "good thing." --- Quote ---I'm gonna put mine in a res file so the user won't have to deal with it. --- End quote --- BTW, I looked through the resource file stuff and didn't see any way to add an OCX. Are you sure that's possible? Or are you talking about something else? RandyT |
| Howard_Casto:
It's an old trick... doesn't always work. You put in in a res file, then on startup of the app you check to see if the ocx exists outside of the app somewhere (check the app path and the system folders) if not you open a file (named after the ocx of course) for binary output, use loadresdata to get the ocx contained in the res file as binary data, "put" it to the file you created, and poof, the ocx is installed. |
| Navigation |
| Message Index |
| Next page |
| Previous page |