[Release] FrodoComm, and FrodoComm Services Host

Quote:

---

Originally Posted by ImInSanDiego

I'm sure that both apps were installed previously, especially since I loaded the FrodoComm User Control into my AXcontainer, but I uninstalled both apps, rebooted, reinstalled them, and then rebooted. I still get the same errors. I've verified that many of your controls are registered, but I see nothing about FCClass.dll. This doesn't appear to be an ActiveX type control since I manually registered it and it still doesn't show up. How is this file accessed? Any other suggestions?

---

Try this, maybe my installer did not register FrodoComm itself correctly.

Browse to ...\FrodoSuite\Frodocomm

find FrodoComm.exe

register it by running "frodocomm.exe /REGSERVER"

Then try it again.

Quote:

---

Originally Posted by frodobaggins

Try this, maybe my installer did not register FrodoComm itself correctly.

Browse to ...\FrodoSuite\Frodocomm

find FrodoComm.exe

register it by running "frodocomm.exe /REGSERVER"

Then try it again.

---

Success!

Now for a new question. I have successfully posted and broadcasted messages as seen in your ServicesTest app, but I am wondering how the CommList IDs get cleared. If you look at the array in my app you can see my app name repeated from when I stopped execution before endprocessing was called. You can also see a couple of services that remain from when I manually killed the servicehost.

You recieve notice through the memberstatuschange event of additions and subtractions.

I must not have something right because I don't have memberstatuschange to choose from. I also don't have Notifybroadcast and NotifySpecific that are called in your test app.

Also, each xxxThread method says "dontcallme"

Quote:

---

Originally Posted by ImInSanDiego

I must not have something right because I don't have memberstatuschange to choose from. I also don't have Notifybroadcast and NotifySpecific that are called in your test app.

Also, each xxxThread method says "dontcallme"

---

Those are events, not functions.

I sent you a PM ImInSanDiego, read it ! :)

You bastard :)

I've been thinking about and writing some basic specs of this exact idea for the last few months.

And I can see EXACTLY where you are coming from it, so I expect it will be very popular indeed.

Just be carefull, because I would hate for any programs out there to become somewhat dependant on this, and for the development to cease for some reason... (just being wary).

Quote:

---

Originally Posted by Shotty

Just be carefull, because I would hate for any programs out there to become somewhat dependant on this, and for the development to cease for some reason... (just being wary).

---

My programs will basically depend on it. :o

I've got faith in the monkey :)

Quote:

---

Originally Posted by Shotty

You bastard :)

I've been thinking about and writing some basic specs of this exact idea for the last few months.

And I can see EXACTLY where you are coming from it, so I expect it will be very popular indeed.

Just be carefull, because I would hate for any programs out there to become somewhat dependant on this, and for the development to cease for some reason... (just being wary).

---

Well it's out now, so really no chance of that happening.
The service launcher is just a convenience, frodocomm is
where the magic happens.

Expect a service that does text-to-speech. More advanced than the one Frodo has made... it will encompass SAPI4 and SAPI5, allowing the user to choose either. Then they could configure the voice, etc. And it will also report back when the program has finished speaking :)