Here ya' Go.........
EDIT: New "InternetRadio" zip uploaded. :)
EDIT 2: fix a few....all good now
Here ya' Go.........
EDIT: New "InternetRadio" zip uploaded. :)
EDIT 2: fix a few....all good now
@bambam - Leave all of the phoco stuff unchecked and then look at the mobilephone.net thread. Works great for me here (although Blue Soleliel is about 50 bucks). Voice commands should work as they are. Make sure that you have unchecked "Use Built-In Voice control" on Page 3 in RR Config. This will allow (counter-intuitively by the way) your voice control to work.
Well, I'm lost as far as this number is concerned. Just to Dbl check, I just DL'd the current WiFiMan PI Net version and checked the skin, skin loads using the correct Wireless_x.png's and plugin working. Sure your are running DFX5 and not DFX4?Quote:
3.) WiFi Skin tries to load wifi_on and wifi_off.png's which are apparently no longer valid with WiFiman .NET 2.0. If the png's are added to the DFX folder, the skin loads but also has Carwings button backgrounds. This doesn't really matter much because Wifiman won't work on my system anyway at this point. It hangs the system on startup of RR. When I can get around it, it can't find my wireless adapter. Not your issue.
Again, lost...hitting the "Valet" button on the new exit menu, locks the skin and brings up the skin locked screen for which you enter the 4 digit code to unlock it.Quote:
4.) I may be missing something operationally (user error), but when using "Valet" I'm not seeing a way to unlock the system. Edit: Seems the "hidden" Hotspot for unlocking is missing.
This was more of a tool when we still had the whole button choosing screens, and as such, was used to rearrange those button chooser screen buttons, not the actuall buttons in the menus. Reason why we now have the list of available cmds, besides being only one screen for all available button choices.Quote:
5.) Not related to this update but I've tried using the DFX Button Editor to eliminate some unused stuff and re-arrange the menu buttons to my liking. After making changes with the button editor, saving and exiting, relaunch of RR shows no changes to my skins.
This is a WIP featue, been started and needs yet a TON of work still...Quote:
6.) Help Button in Menu 2 doesn't display help.
??, As in which srcreens, this skin has tons...Quote:
7.) No top quicklaunch bar on a few screens. (tough when using voice)
Good call...I really should now remove that very old "Built-In Voice Control" in RR's core, it both very outdated and worked poorly compared to Jebus's RRVoice plugin now.Quote:
Voice commands should work as they are. Make sure that you have unchecked "Use Built-In Voice control" on Page 3 in RR Config. This will allow (counter-intuitively by the way) your voice control to work.
Probably expect the next RR release to have that removed...
---------- Post added at 12:23 PM ---------- Previous post was at 12:14 PM ----------
Not, Till such a future date or release, continure to use RRVoice. 5.1 Does not include any of its own voice control yet.Quote:
As far as voice, is it built in to DFX 5.1 now or do I need to use RRVoice? I can't for the life of me find that answer or how to set it up. I just went through the entire new DFX 5.1 help and there is nothing in there.
Thanks, Didn't know it was an executable. System just showed and tried to open it as an archive.
Ya, for some reason the App store changes the ext when going to dl it, as it was uploaded as the regular exe.
1st. I had still had access to the red apple Donation patch at the generosity of John. Would that cause any issues? When I patched with 5.1 I see the splash screen says "5.1" then the disclaimer and donation screen showed up anyway. I re applied RA Donation Patch and seemed to work except the splash said 5.0 again, no biggie. Will that old patch cause any issues with DFX itself?
2nd. Been having issues with color changer. When I select a color and say "Change Font Color" DFX starts applying and reloading but hangs. There is a black area to the left of my screen and all I can see is "Trying". This is what it looks like. This happens when trying to change colors, themes, or even restore themes.
We are working on correcting the bugs that have been brought up so far...
Unless you want to be a beta tester, I recommend waiting till the next patch is out within the week taking care of some bugs and issues.
1) Glad that is fixed now
2) Still working on the camera stuff, some bugs and kinks to work out
3) I have not downloaded and tested the new WiFi, I will get that taken care of soon
4) Oversight on my part, and has been fixed in the next patch, due out soon. You will press and hold the valet button, and choose what you want that button to do. Lock & Hibernate, Lock & Stand By, Lock and Shut down, Lock and pause any playing audio.
5) The button editor now just adds the option to the press and hold list. EA: If you use the button editor and add XYZ application and path, it will then be in the list to choose form when you press and hold a main menu button.
6) The help function is a work in progress and far from being completed.
7) Some screens just do not have the space at the top for the indicators and quick links. When using voice, it is highly recommended to use a hardware button to trigger the system to listen.
---------- Post added at 02:29 PM ---------- Previous post was at 02:24 PM ----------
---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------
Yikes! That is going to happen with ANY settings change in the skin for now, Major Bug! It is something Blue is going to look into the RR source code and correct.
---------- Post added at 03:27 PM ---------- Previous post was at 02:31 PM ----------
---------- Post added at 03:33 PM ---------- Previous post was at 03:27 PM ----------
As far as phone, Phoco was discontinued by it's Author a few years ago. This means that it will not work with most modern phones. Installing the MobilePhone.net plugin is highly recommended. There is no 100% bullet proof phone solution for RR currently, so it's really a matter of getting your hands dirty and testing things out.
Thanks for the update John.
I believe I was among those who downloaded the patch right after it was announced. I really enjoyed new design the patch provided to some of the skins. Unfortunately, I was stupid enough to press new valet button just on the 5th minute and faced the issue already mentioned few posts above, system locked and no skin shown for entering the pin.
So I played with .ini as Driven01 suggested and unlocked my system, but DFX appeared with all the buttons being empy (no text on them), the bottom line was ok. Since I was actually on my way, I decided not to lose time looking for the reason what went wrong and just re-install the DFX5. I made a "clean" DFX5 install and everything worked propertly, so then I tried to install the patch again.
And finally there goes my problem - I could not start patch installation as everytime I clicked on the file there was immediately warning window poped up saying "Setup could not locate the RideRunner application folder. Setup will now exit".
Any suggestions, what should I do to get the patch installed on my system?
Thanks Blue and John. Looking forward to the next release and thanks for the info on the Button editor (I guess I misunderstood how I thought it worked. No biggie) And let me say that even with the little niggles here and there, this is by far the best RR Skin to date compared to the others. Very feature rich! I understand this is a work in process and quite familiar with Beta software. And it's FREE. (although I did donate 'cause I like DFX so well). Gotta expect some probs here and there. Just wanted you guys to know what I ran into this morning and I'll happily await the fixes for what can be fixed.
@Blue - on the WiFi thing, it could be because I had previously installed the old wifi manager by mistake and there may still be some remnants of that lurking about. Will look into it. On the voice control issue there are many screens that don't have the top bar with the voice activation icon available. I understand that there may not be space for it on some screens. To me, it's more of an oversight (maybe - could be on purpose) that RRvoice needs to have a physical input of some sort to activate it. I have other voice recognition software that listens for a specific command to activate it and then say a second command to have it launch what I want displayed. This is how I feel RRVoice should work. Not knocking Jebus, it's a great little piece of work. Adding that one small feature would make it perfect.
On the Locking feature, if I lock the screen I don't get an unlocking screen. It goes back to the Main Menu in a locked state. Clicking in the upper left hand corner does not display an unlocking screen if that's what's supposed to happen.
As far as what screens don't have the quicklaunch at the top...
Calendar (I know that the calendar isn't finished, but should still have the quicklaunch)
Quite a list isn't it?! Seems that most of the sub-skins don't have it. Not gripin' just bringin' it up.
What I'm going to be using this in is a Motor Home using a touch screen and voice commands. I really don't want to have to touch a thing on the screen if possible. That's why the availability of Voice activation is kind of important to me. It's bad enough that I have to touch the screen to activate voice control in the 1st place. If RRvoice listened for an activation command none of this would be an issue just as long as it understood the commands.
Last and certainly not least. If my system is the ONLY system that these problems are occuring on, I'm fine with that. Won't be the 1st time, won't be that last.
Thanks again guys for all your time, hard work, and dedication to this project!
---------- Post added at 05:19 PM ---------- Previous post was at 05:09 PM ----------
@Kadyroff - didn't experience that at all after changing the .ini !! No clue. Maybe just needed a reboot?