|
||||
Quote:
Its not working either way, i redid the whole OEM, got all the files to copy properly, still wont work. im boggled, i think i need to sleep on it and something will come to me tomorow just to note, the cab file works because it loads it in the windows startup folder, i may do the same and call it a day, it will also allow me to cut the package size down about 1.5 megs wich is a LOT. EDIT Fixed it.... the problem was that the systems registry entries were being written AFTER the OEM package was processed, erasing the entries for the threadedSMS to take over messaging. once I renamed the DSM & RGU to have them process 2nd to last (zREG process' last) it worked fine, and doesnt need to load in startup. HOOORAY, k going to bed, been working on this for like 7 hours. Ill update tomorow |
|
||||
Thanks.
This was one of the items I was having an issue with when I brought your Threaded SMS app over to the R3 Kitchen. I just posted about it over there. For me, it works, but only when it's running in the foreground. Which kind of defeats the point of having it. Hopefully you post the fixed OEM so that the entire kitchen doesn't have to be re-downloaded (but I'll live if I have to get the whole thing again). Congrats on getting it fixed- we all appreciate the long hours!
__________________
The only way of discovering the limits of the possible is to venture a little way past them into the impossible. Any sufficiently advanced technology is indistinguishable from magic. |
|
||||
Another bug im getting is lockups on startup randomly, and items on the today screen are not updating until after a soft reset. lets say i deselect the messaging and inbox today plugins, and select the weather panel plugin. when i get back to the today screen, the plugins havent changed. when i go back into the today screen config, the choices i made are still correct, but it just doesnt update the today screen until after a soft reset.
|
|
||||
Quote:
![]() ![]() |
|
||||
Quote:
I think next time I see helmi I will inquire about the feasability of just renumbering some of the problematic UUIDs in the kitchen so that this doesn't keep happening. It must be doable since the old kitchen never had this problem, and it would prevent a lot of hassle tracking down issues like this one. |
![]() |
|
|
|