Wheel-2-Unlock - NO LONGER UNDER DEVELOPEMENT!!! - Page 8

**jason25** · #71 (**permalink**) 10-06-2008, 09:51 AM

Quote:

Originally Posted by rainfreak

Update:

All in all I am closer than ever but believe me when I say that it is no where close to being ready for any kind of release. I like all of you too much to offer a free, customizable hard reset app to you

lol, sounds nice =D>

**rainfreak** · #72 (**permalink**) 10-09-2008, 07:15 PM

Just to let everyone know, I am still working on this and I got quite a bit more done last night. I don't want anyone thinking that I have abandoned this project, I just have a lot of other responsibilities that have to come first. I have definitely fixed the issue with the battery drain and I think I figured out why it was not always unlocking when the motion was complete. I am still trying to understand why it will not run when TF3D is, which is a big problem for me as I still use TF3D. That and the issue is driving me crazy from a programming stand point because it is obviously something that I screwed up since Sensorlock, S2U2, and all the others work fine with TF3D running.

I am chillin' with the wife when I finally leave work tonight, but she is working most of the weekend, which will give me some solid time to work on it some more in the next few days. I will try to keep you all posted as I go and once I get a semi-stable release ready I will start PMing people with a download link. At this point I have no idea when that will be (hopefully soon), but I wanted everyone here to know that I haven't gave up on this.

Thanks for all of your interest, patience and understanding.

**syanni85** · #73 (**permalink**) 10-09-2008, 07:24 PM

Quote:

Originally Posted by rainfreak

Just to let everyone know, I am still working on this and I got quite a bit more done last night. I don't want anyone thinking that I have abandoned this project, I just have a lot of other responsibilities that have to come first. I have definitely fixed the issue with the battery drain and I think I figured out why it was not always unlocking when the motion was complete. I am still trying to understand why it will not run when TF3D is, which is a big problem for me as I still use TF3D. That and the issue is driving me crazy from a programming stand point because it is obviously something that I screwed up since Sensorlock, S2U2, and all the others work fine with TF3D running.

I am chillin' with the wife when I finally leave work tonight, but she is working most of the weekend, which will give me some solid time to work on it some more in the next few days. I will try to keep you all posted as I go and once I get a semi-stable release ready I will start PMing people with a download link. At this point I have no idea when that will be (hopefully soon), but I wanted everyone here to know that I haven't gave up on this.

Thanks for all of your interest, patience and understanding.

Sweet, Thanks bro!

In my opinion, you should still release an alpha even with it not working with tf3d.... I think i may convert over to the FFEWidgets today screen (Omnia) when it has enough widgets and functionallity... would love to test it even while it doesn't work with tf3d///

plus, think of it this way... if it doesn't work with tf3d, i'm sure there are people here and at xda who could contribute to your work based off an alpha!!

Simply put, when you release the alpha, the development would speed up DRAMATICALLY!!!

Thanks again bud! Can't wait for this!

**rainfreak** · #74 (**permalink**) 10-09-2008, 07:38 PM

Quote:

Originally Posted by syanni85

Sweet, Thanks bro!

In my opinion, you should still release an alpha even with it not working with tf3d.... I think i may convert over to the FFEWidgets today screen (Omnia) when it has enough widgets and functionallity... would love to test it even while it doesn't work with tf3d///

plus, think of it this way... if it doesn't work with tf3d, i'm sure there are people here and at xda who could contribute to your work based off an alpha!!

Simply put, when you release the alpha, the development would speed up DRAMATICALLY!!!

Thanks again bud! Can't wait for this!

I absolutely agree and know well that the development from others (if they are interested) will be off the hook. And I do not mind at all skipping the irritating TF3D issue and releasing it before I figure that out. But...

I want to make sure that I have fixed the issue with the unlock when the motion is complete, as I have not had a lot of time to test it. Also, I used the most janky and crude images that I could for the app as I just wanted to get the programming done before I worked on the asthetic properties of it. I literally took about 3 minutes in Photoshop to make an image the right size for testing. And because of this, I also have not built the ability for skinning into it yet.

So all in all, I am totally cool with releasing it when it is pretty stable and allowing people to help with the project, but I also want to ensure that it is indeed working correctly, and also that it is utilizing xml for the skin. Basically get the design of the app the way that I want it, then let others go from there with it. That way others can start working on the image work for me because I know what they can do is far better than what I can do graphically.

**jason25** · #75 (**permalink**) 10-10-2008, 05:13 AM

sounds good, I understand you not wanting to release something that you don't feel is up to par or underestimate your quality of work. However, as I have learned once again this week, sometimes it helps getting input from other develpers. It is just another mind catching a possible oversight.

I have been stumped on the programming of a banding unit on a particular R&D part for one of our machines, so I had to get the guy from our Tech. Center who built the machine to lend a hand. It ended up being a code in 100 lines of program that I missed. doh