I don't know how to explain it very well, so that's why an image value is more than one thousand words, I hope my screenshot help.
Thank you.
EDIT:
As you can see in the first id init, I'm pointing to a rectangle that has some information about id init constructor/method/selector, but this information comes from apple NSObject init I guess, and I want my constructor/method/selector prompts extra information while selecting in the method fill helper, as you can see in the second id initWithGPSPointNum ... there is no information, because I don't know how to put there the information I want.
The help hints come from the installed docsets.
You can generate and install docsets for your own custom classes and install them in Xcode to get this extra information as well as auto-completion.
One way that is convenient is appledoc
This uses a convenient and familiar syntax, and produces web formatted output as well as docsets and can even be configured to generate and install the docsets automatically.
Related
I am trying to change the number of custom fields I can create in OrgangeHRM PIM section.
I have found a few articles on this site that say what part of the code to change but non saying where to find the file where the code is stored is in.
If anyone can help then that would be great.
I am running version 4.0 of OrangeHRM.
Thanks
orangeHRM have slots for custom field (i dont remember, but i think 10 slot in orange 4.0), you can use this for put what you need.
Out the box, you can follow guides for add more custom or pre-format fields, but not is more recomendable, this can make broken code.
meanwhile, you think work out the box, remember orangeHRM is a symfony based software, if you know how work symfony (MVC framework), work it whit OrangeHRM is more easy
good luck
I'm trying the Branch.io API and I think I'm getting a weird problem because I'm not able to create my links properly: I can use the link for starting the app without parameter: this link http://4t3i.app.link/KDSYTMnSZs.
It works perfectly but as soon as I try to put some parameter following the doc for appending query parameters, it returns a File Not Found Webpage.
I tried:
https://4t3i.app.link/a/?&jobId=saucisse
https://4t3i.app.link/a?%24deeplink_path=article%2Fjan%2F123&%24fallback_url=https%3A%2F%2Fgoogle.com&channel=facebook&feature=affiliate&user_id=4562&name=Alex (that's the example they give)
I have the feeling I'm really missing something but no idea what. Is that so easy to add parameters: just a/ and then appending parameters??
Alex from Branch.io here:
We recently made a major back-end change to accommodate some new technical limitations that Apple imposed with iOS 9.3.1, and unfortunately it looks like we didn't fully update all our docs yet!
Your links are correct, but the /a is no longer necessary. So they would be:
https://4t3i.app.link?&jobId=saucisse
https://4t3i.app.link?%24deeplink_path=article%2Fjan%2F123&%24fallback_url=https%3A%2F%2Fgoogle.com&channel=facebook&feature=affiliate&user_id=4562&name=Alex
When you open these, you'll be able to see the link clicks coming through on this dashboard page
Thanks for noticing this. I'll make sure we get the documentation changedto reflect the new system.
Edit: also note that those examples above create new links with the specified parameters. If you simply want to append an additional parameter to an existing link, you'd do this: http://4t3i.app.link/KDSYTMnSZs?jobId=saucisse
I am new to Pure Data and have no idea why the following are displayed after I clicked help:
I am using Windows 7 and pd-extended 0.43.4.
This error (xy ...could not crate) means that this abstraction or external failed to instantiate. It could be that you don't have it installed, or it is not in Pd's search path so it can't find it. In the patch you are opening those objects seem to be used. In your case that might be the help file.
This is an answer on the pd forum by user whale-av already,
whale-av:
[midiin] and [sysexin] are not supported in windows. Some people have written patches to get around the lack of sysex, and instead of midiin you can use [ctrlin] [notein] etc.
[powtorms~] [mstopow~] do not exist as far as I know even in vanilla for windows, and in the windows extended 0.43.4 release they do not. I remember seeing that they were in a Linux vanilla build, and in a very old Pd build for XP.... so you might be able to find them......... someone might have built them as an external that you could add to your pd/extra folder and then use them like any other object. If you have opened someone elses patch then it is possible that they used those objects in that patch, but you do not have them so they will not "create" and will just show the name in a red dotted box instead of a solid black outline.
[scalar] does not exist, but [scalar-help] does and that explains how to use scalars....... which use other objects but not [scalar]
So, basically, not all objects exist in all versions of Pd, and certainly not under all operating systems.
I like to use these to debug (can you tell I'm a noob?) and have left them in my code as is when deploying to the app store. Are there any negative implications for this you can personally think of?
I have looked at these resources and I am getting the feeling it's not a good idea:
http://doing-it-wrong.mikeweller.com/2012/07/youre-doing-it-wrong-1-nslogdebug-ios.html
https://developer.apple.com/library/mac/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/LoggingErrorsAndWarnings.html#//apple_ref/doc/uid/10000172i-SW8-SW7
This was also a good resource:
http://www.theonlylars.com/blog/2012/07/03/ditching-nslog-advanced-ios-logging-part-1/
That said, when you ship to the store and DO keep NSLogs in there, what have you logged?
Create a snippet with the above settings. Where it says "debug statement", replace that with:
<#debug statement#>
Now, since the completion shortcut is set to "NSLog", every time you start typing NSLog, it will autocomplete to this snippet and you will have the "debug statement" part selected and ready to type over.
You'll never have to worry about commenting out your NSLog statements again, and you'll never have to forget about using #if DEBUG since the completion shortcut is what you would type anyway.
Apple's Official Documentation for creating a Snippet (I've included this link because I think it's really kind of sad that this is apparently the only way to do it?)...
And my explanation...
Copy and paste the following code into Xcode:
#if DEBUG
NSLog(<#debug statement#>);
#endif
Select the entire code block you just copy-pasted. Click, hold, and drag this code block down to the snippets section (usually in the bottom right corner).
Select this snippet to get a screen like this:
Click "Edit" and fill out the details. Give it a title and description. Leave platform on "All", and language on "Objective-C". Set the completion shortcut to "NSLog", and leave the completion scope on "Function or Method" (what this option defauts to may depend on where you pasted the code to originally and where you dragged it from).
As Aaron Brager's answer points out, NSLog could be a performance concern, particularly in loops (also in places that don't seem very much like loops but actually are, like cellForRowAtIndexPath...).
But more importantly, you may be exposing information you don't necessarily want to be made publicly available.
I'm not saying there doesn't exist something that might be useful to include to present to the end user in the log statements, but personally, I've yet to find it. How many times have you ever investigated the output of an app's log statements to diagnose an issue you were having with it? How many times have you contacted an app developer and they asked you to check these statements to help diagnose a technical issue you were having?
The Mike Weller post you linked makes the right call. NSLog is for user-facing warnings.
There also might be performance issues, especially within loops, since it uses a string formatter.
You can and should use DDLog or other tools to ignore the debug messages when you make your release build.
I am creating a Setup for my .Net Application using WIX.
I want to check the existence of a file before installing my WIX SET UP as a Dependency.
If that file not exist then a message should be displayed.
Any help would be appreciated.
To check for the existence of a file you can use the FileSearch-element in combination with the DirectorySearch-element. For an example you can take a look at How To: Check the Version Number of a File During Installation (you don't have to use the version part for your needs).
For displaying the dialog you can create your own SpawnDialog like described here. Another alternative would be to add the text as property to the Welcome-dialog and set the property based on your findings. Still another way would be to include a second Welcome-dialog and then invoke the needed one as described in this stackoverflow-question.