Where are user defaults plist files stored in iOS8? - ios-simulator

I can't find preferences .plist file, because Preferences folder is empty.
To get Library folder I use:
println(NSSearchPathForDirectoriesInDomains(.LibraryDirectory, .UserDomainMask, true)[0])
Xcode 6 beta 5, iOS Simulator

The folder hierarchy has changed under iOS8.
All preferences are now stored under the common /Library/Preferences folder. Notice, this is not the Library folder under your app's container, it's the general Library folder.
For the simulator, the exact folder is:
~/Library/Developer/CoreSimulator/Devices/<Unique Simulator ID>/data/Library/Preferences

Related

Qt renaming path of the project

sometimes when I rename the path to a qt project, it cannot be run even though I clean qmake and rebuild it!!! the path does not contain any space. and the project is completely correct and I know that the error is for path renaming , for example when I rename :
D:/abd/projects/LAND_2/Land_QT/...
to
D:/abd/projects/LAND_2/Land2_QT_SA/...
it cannot be build and says that some include file is missing(but the file is there!).
what is the problem?
I work with dynamic qt5.2 on windows 7.
Edit:
when I copy the project folder to a new directory( a path upper than current path) then the project can be build and run.
When you rename the path to the project, go to the project folder and delete the file with .pro.user extension. Open the project and Qt will ask you to configure the project. Choose the required kit, build and run the project.It should build successfully now
If you have changed path multiple times the .pro.user file is created multiple times delete all files with this extension and compile

Qt 5.2 Including External File into an Android Package?

How to include an external file into 'apk' ?
Example:
There is "123.txt" in the main directory where .pro file exists. What should I add to pro file to put "123.txt" into apk.
I tried DEPLOYMENT, DEPLOYMENTFOLDERS. But they only works with Symbian and Windows CE.
There are two ways to do it, both mentioned under "Porting an Existing Qt Application" on Qt 5.1 Documentation For Android.
Bundle them into a qrc file (works cross platform)
Add them to the "assets:" directory (Android specific)
For #2:
The "assets" directory will be created when you build the project. I have found it easiest to use the "INSTALLS" qmake variable to copy the files into the directory before it is packaged into an apk. The following is from a qmake file for a project I made. Note that for INSTALLS, the path to assets reads "/assets", not "assets" as you would expect. (It actually ends up in a subdirectory of the Android build workspace.)
To access the directory from the code in android, you use "assets:". (In the example, /assets/Samples ==> assets:/Samples.)
# - setup the correct location to install to and load from
android {
# android platform
# From: http://community.kde.org/Necessitas/Assets
SAMPLES_INSTALL_PATH=/assets/Samples
} else {
# other platforms
SAMPLES_INSTALL_PATH=$$OUT_PWD/Samples
}
# - setup the 'make install' step
samples.path = $$SAMPLES_INSTALL_PATH
samples.files += $$SAMPLE_FILES
samples.depends += FORCE
INSTALLS += samples
You can use the Qt Resource system. By default, all Qt applications can access the contents of a qrc file using the ":/" prefix or the URL scheme prefix, "qrc:".
The other approach is to deploy the resources into the package's assets directory. It is the best option if you want to achieve better interoperability with the Android APIs. You can access all resources in the directory using the "assets:" prefix. Unlike qrc, this approach is not a cross-platform solution.
When you build your project, a folder named "assets" is created in the Build-Directory/android-build/. After copying your files in the assets directory, you can add these to your pro:
deployment.files += MyFile1
deployment.files += MyFile2
...
deployment.path = /assets
INSTALLS += deployment
The files in assets are readonly. So you should first copy it to some other location if you want to change them:
QFile dfile("assets:/MyFile1");
if (dfile.exists())
{
dfile.copy("./MyFile1");
QFile::setPermissions("./MyFile1",QFile::WriteOwner | QFile::ReadOwner);
}
Specific to User2400925
In QT 5.1 I had used to copy the database from Assets folder to the home folder of the user, if the file does not exist. Which can be used by the App.
You may go through this link
One more simple way to do that:
1) Add this string into your .pro
ANDROID_PACKAGE_SOURCE_DIR = $$PWD/android-sources
2) Create android-sources folder in your proj folder. Put anything you need into android-sources/assets/. You can also put there any other files, such as AndroidManifest.xml or android-sources/res/drawable/icon.png that you want to be copied and updated into the target bundle.
One more simple way to do that:
Add this string into your .pro
ANDROID_PACKAGE_SOURCE_DIR = $$PWD/android-sources
Create android-sources folder in your proj folder. Put anything you need into android-sources/assets/. You can also put there any other files, such as AndroidManifest.xml or android-sources/res/drawable/icon.png that you want to be copied and updated into the target bundle.

opening Flex project without .actionScriptProperties

I need to import a flex project into FlashDevelop.
However I am unable to find the .actionScriptProperties file.
How would I be able to import the project?
It would be great if someone could help me out with it.
Usually Flex Builder project contains:
src/ directory - source files (.as and .mxml)
libs/ directory - .swc files (if exists)
Usually FlashDevelop project contains:
1) src/ directory - place here files from src directory of FB project
2) lib/ directory - place here .swc files (if exists) from libs directory of FB project
3) on each swc files (if exists) you need make right click and select "Add to Library".
4) Make right click on main class file and select "Document Class"
This is main. May be there are other files. But I can not say what you have because I not know what files you have.
actually i canĀ“t import a FB project to FD whit the options in the menus but i can fix it creating a new project in the folder of the FB project and putting files in folders identified by FD it works for me

iPhone simulator sandbox location in Xcode 4

Xcode 4 seems to have changed the deployment location of the application data which previously used to be in:
Users/INSERT_YOUR_USER_HERE/Library/Application Support/iPhone Simulator/
Does anybody knows where is it now?
Thanks,
Raj
PS: I am beginning to hate Xcode 4! Sick!!!
The Application is Sandboxed in the location you specified is correct.
/Users/INSERT_YOUR_USER_HERE/Library/Application Support/iPhone Simulator/
That is this is the place where the Application(.app file) the installation file will be there.
I was wondering that you were searching for the build file or the binary file(.ipa). In Xcode4 they have changed it. Previously in Xcode 3 versions the build file will be in the folder where you have created your Project along with all your .h and .m files.
Now the build file is in this Path
/Users/YOURUSER/Library/Developer/Xcode/DerivedData/YOURPROJECTNAME_SOMETHINGSOMETHING/Build/Products
EDIT: More simple solution would be In the left side Navigator window in the Project structure under the Products Folder you will find your app. Right click on that and select open in finder will you take you to folder containing your app .app file.
If you want .ipa file just drag and drop the .app file into itunes it will convert that into itunes file and again rightclik and show in finder will give you the ipa file
On my mac the folder never changed.
The sandbox of each application i have in the simulator can be found in:
${HOME}/Library/Application Support/iPhone Simulator/<SDK_VERSION>/Applications/<GUID>
If you right click on YOUR_APP_NAME.app file in xcode, it will take you to the sandbox folder.
You can find that in the following path:
/Users/User/Library/Developer/Xcode/DerivedData/Your-Project-Name/Build/Products/Debug-iphonesimulator/location.app

Qmake does not support build directories below the source directory

I have created an application that compiles and runs like a charm on OS-X. I would now like to start getting it to work on Windows. To start, I copied the project to a windows machine and just tried to compile, but got this error:
:: warning: Qmake does not support build directories below the source directory.
Any ideas?
Set the shadow build directory to some folder on the same level of your project directory:
folder/
project/
project-shadow-build-release/
project-shadow-build-debug/
You can do this in the "Projects" view, via the toolbar on the left. To me, this warning was just an annoyance, a project never failed to build because of it.
Don't copy your project.pro.user file when you are copying a project from one machine to another, or from one directory to another. When you open the project, Qt Creator will offer to create a new build directory in the proper place.
Andref gave the correct answer to resolve this warning, but you may want to understand why this requirement exists.
In fact, the build directory must be at the same folder level as the project (i.e. it can't be above or below). The reason why is that the linker is called from the build directory. Hence, any relative paths to library files will be different than what you entered in your project file.
It kinda sucks. I like to put all intermediate files in their own folder. But you simply can't with qmake.
.pro.user are generated files by Qt Creator. They are unrelated to qmake and should not be touched (and not put into a VCS for that matter)
Just remove the files with the pro.user extension , worked for me
I also got this, trying to compile a project created on linux.
Another way to solve it is to change the paths in the .pro.user file (in the directory of your project)
Right Click on a project: Set As Active Project
Click on the Projects button (The one with the spanner image)
Edit build configuration : Debug / Profile / Release / and change the default directories, OR just uncheck the Shadow build check box.
The Build directory path should now change to black, from red

Resources