When UI is tuned, the interface iteration view is not very well tuned, and the following is an instant UI software: Reveal. The reveal tool is suitable for debugging interfaces created by non-Interface builder, Xib and storyboard created in Interface Builder are not always competent in enterprise development
Reveal Address: http://revealapp.com
After downloading the installation package, use the Reveal connection simulator to debug:
Reveal official introduced several ways to make the reveal connection simulator, all need to modify the project file. However, if the engineering documents are modified, it is quite unfriendly to have all the people involved in the development of the project equipped with reveal. This sectionto introduces a method that does not modify any engineering document, in actual use, this method is the simplest and most convenient. The steps for this method are as follows:
First open the terminal, enter VIM ~/.lldbinit create a file named. lldbinit (If you can't find this file, you can do it in the terminal: Defaults write Com.apple.finder appleshowallfiles YES Display the hidden file), and then enter the following into the file:
Command alias Reveal_load_sim expr (void*) dlopen ("/applications/reveal.app/contents/sharedsupport/ios-libraries/ Libreveal.dylib ", 0x2);
Command alias Reveal_load_dev expr (void*) Dlopen ([(nsstring*) [(nsbundle*] [nsbundle Mainbundle] pathforresource:@ " Libreveal "oftype:@" Dylib "] cstringusingencoding:0x4], 0x2);
Command alias Reveal_start expr (void) [(nsnotificationcenter*) [Nsnotificationcenter Defaultcenter] postnotificationname:@ "Ibarevealrequeststart" object:nil];
Command alias Reveal_stop expr (void) [(nsnotificationcenter*) [Nsnotificationcenter Defaultcenter] postnotificationname:@ "Ibarevealrequeststop" object:nil];
This step is actually set up for the Lldb 4 aliases, in order to facilitate the subsequent operation, the 4 aliases have the following meanings:
Reveal_load_sim load reveal debug dynamic link library for simulator
Reveal_load_dev dynamic link library for real machine load reveal debugging
Reveal_start start reveal Debug function
Reveal_stop End reveal debugging function
Next, we add a breakpoint to the Appdelegate class's application:didfinishlaunchingwithoptions: Method, and then right-select Edit Breakpoint
Click "ADD action" on the right side of the "Action" item and enter "Reveal_load_sim" to tick "automatically continue after evaluating" option on options
After opening reveal, run the program. After the run is complete, click the no connection in the top left of reveal to select your current app to debug the currently running interface on your emulator.
Note:
Simulator project and reveal is not real-time connection, if you change the interface on the simulation to continue debugging on the reveal, just go to the no connection to re-select the current app (or can command + R) can be, equivalent to refresh the interface.
If repeatedly debugging can not find the current app in no connection, then find the Reveal package, regardless of the package name is changed to Reveal, no suffix, and then restart Xcode, Reveal, should be no problem, this is because we compile, Need to adjust the resources within the reveal package, if the reveal name is not correct, the last read path is definitely wrong, not the resources in the package, reveal can not play a role.
Reveal--ios Program Interface Debugging Tools
