View Single Post
  #167 (permalink)  
Old 09-20-2007, 07:00 PM
codyppc's Avatar
codyppc
VIP Member
Offline
Location: kansas city, missouri
 
Join Date: Sep 2006
Posts: 647
Reputation: 2642
codyppc is a VIPcodyppc is a VIPcodyppc is a VIPcodyppc is a VIPcodyppc is a VIPcodyppc is a VIPcodyppc is a VIPcodyppc is a VIPcodyppc is a VIPcodyppc is a VIPcodyppc is a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via AIM to codyppc
Quote:
Originally Posted by wowthatisrandom View Post
alright cody lets try to answer each question....

1.DialedID it only works when CloseApp is 0, CallerID is 1 or 2, DialedID is 1 & SLIDE is already running in the background. WHY? Simply because don't want to slow down the normal dialing process. also theres no way to make it stick longer yet... its just for the dialing screen.

2.The cool "dialing screen is the DialedID screen that you were talking about in question 1... and like i said its only for dialing i believe it goes away once the call is connected.

3.slide2unlock has its random f ups... i dont know what causes it they happen to me too... the things i found most useful in stopping them... add as little as you can on the app... for example im only using slide2unlock and a custom background... im not showing weather, appts or using callerID or dialedID... if it stops openning all the time then i usually just tape the Slide.exe in program files\slideunlock and that usually fixes it... i dont know what actually activates it on wakeup

on another note.. any edit u do make in the reg or with the configurer (which i have yet to try i can edit the reg just as easy) you still need to stop ilock and restart it again b4 all the changes will take effect...

finally keep checking that link in the first post he makes updates at least once a week lately small things that have been improving the performace of the application...

thanks buddy for the insight.

cody