I just moved my C++ Builder XE3 to a new machine and I cannot find the file that stores all the default settings for the program. e.g. Debugger fonts and colors, etc.
Related
I am using "Tools - Options - Environment Options - Delphi Options - Library-Win32 - Libary path" variable to keep the semicolon-separated lists of paths for the directories in which I am keeping *.dcu files (Delphi compiled units) in the older Delphi versions, e.g. Delphi 2009.
Now I have Delphi 10.4 Sydney and it does not have such option. Which Delphi 10.4 Sydney option replaced the older Library path?
My guess is that Delphi 10.4 used 'Tools - Options - IDE - Environment Variables - System Variables - BDSBIN' or its 'User Sytem Overrides' as the Library Path. But I have confusion about this, becase my installation contains the value "c:\program files (x86)\embarcadero\studio\21.0\bin" currenty and I am afraid to put additional directories here. The name "BDSBIN" seems so venerable that it may be allowed to contain only one directory only? Or is it possible to add semicolon-separated directory list here as well?
Context: I am trying to use https://github.com/theilgaz/FGX in my Delphi 10.4 Sydney and it puts all the dcu files beside the pas files. So - my intention was to copy dcu files in the separate library directory and add this directory to the Library Path and I am not sure wheter the BDSBIN is the library path for Delphi 10.4 Sydney or should I look in other Delphi 10.4 Sydney environment variable for the list of library paths?
Ever since Embarcadero released its first RAD Studio in 2010 both Delphi and former C++ builder share the same IDE.
So in order for IDE to now support two programming languages at the same time certain options that are language specific had to be grouped together.
This is why you can now fin the mentioned Library settings in Tools>Options>Language>Delphi Options>Library instead.
And if you would have C++ builder licence as well then the library path settings would be found in Tools>Options>Language>C++ Options>Paths and Directories
In Delphi (Berlin), I create a new win32 package and component. I compile it and it creates the default Unit Output Directory of .\$(Platform)\$(Config). Now after installing I need to set the System Library Path correctly so that I can use it in new applications. Should I set this to the dcu path (.\$(Platform)\$(Config))?
If I do, I then need to compile the component for each variant of platform and Config that needs to be supported [(Win32/Win64)/(DEBUG/RELEASE)].
Is this correct? Maybe it would be better to always point to the RELEASE path?
This is probably something stupid I am doing but I have upgraded from 2007 to XE6/7 and I can't seem to find the Type library editor in the new version.
I understand the TLB formats have changed in later versions, I have Myproject_TLB.pas style files which compile OK but I can't change them.
The help file seems to suggest the Library editor is still there but I can't find a way to get to it, the "View/TYpe Library" option is greyed out.
Can someone point me in the right direction, I need to add some more properties and the help files are not useful.
The Type Library Editor is still present but is now an embedded editor for the RIDL file type. As per David's comment, the IDE now uses this RIDL file format as the storage format for type libraries, rather than the TLB file.
When you open a RIDL file in the XE6+ IDE, you will find a very familiar editor interface - basically the Type Library Editor. However, instead of the old Text tab alongside Attributes, Uses, Flags etc etc along the top, it is now reached via the bottom tab strip. The RIDL (Text) view is presented in the Code tab whilst the Type Library Editor style view is presented by the Design tab.
All you need to do is convert your TLB files in your D2007 project to the RIDL format and add these RIDL files to your XE6+ projects. The TLB files will be produced from these RIDL files as needed by the IDE similar to the way that binary RES files are produced from RC resource scripts.
The old Type Library Editor also supported this RIDL format, so one way to get your old TLB files into RIDL might be:
Open the TLB file in the D2007 IDE Type Library Editor
Select the library root node in the hierarchy
Switch to the Text tab
Select the entire contents
Copy/Paste into a text editor and save as a file with
a RIDL extension
Add that RIDL file to your XE6+ project
You can then choose to modify your Type Library either by directly editing the RIDL or using the Design interface, which will perhaps be more familiar to you. Whichever option you choose however, it is now the RIDL file which should be added to your version control, not the TLB.
If you do not have an older IDE available, or if you simply prefer, you can use a command line utility provided with Delphi to do the conversion:
tlibimp -I foo.tlb
Will create the foo.ridl file for the specified foo.tlb input file. Note that this form of the -I option is not supported on older versions of tlibimp but should be supported by the version provided with Delphi 2010 and later.
If you get an error saying that you need a "+" or "-" tagged on after the "I" option, then you are running an older version of tlibimp, perhaps being found on your path.
I would like to use the lib https://sourceforge.net/p/zbar/news/2012/03/zbar-android-sdk-version-01-released/ with delphi XE5, but the lib and. Jar and. So, You can use it with delphi XE5, how do? I need to read the barcode on my webcam!
Take a look at Using a Custom Set of Java Libraries In Your RAD Studio Android Apps. I understand that there was a lack of information on this topic in 2013, but now it is described in the documentation.
There are two different approaches that you can follow to add your Java libraries to your application for Android:
Use the Project Manager to add your Java libraries to your application. This is the simplest approach, you only need a couple of clicks. This approach should work for most people.
Create and deploy a classes.dex file manually. This approach allows you not only to add libraries to your application, but also to modify the built-in RAD Studio Java libraries for Android, or remove those that you do not need.
Add a Java Library File (.jar) Using the Project Manager (XE7 Way)
In the Project Manager, extend the Target Platforms node of your project. Within the Target Platforms node, extend the Android node.
Right-click the Libraries node and select Add.
In the dialog box that opens, select the .jar file that you want to add to your application for Android, and select Open.
Now the Project Manager displays your custom Java library under the Libraries node.
You can now use your Java library.
Remember to create a native bridge file for your Java library if you do not have one yet.
Create and deploy a classes.dex file from JARs manually (Old Way)
Once you have determined which JAR files your Android applications need, you can create a classes.dex file from them.
To create a classes.dex file, you need to use the command-line tool dx. You can find this command-line tool at C:\Path\To\Embarcadero\Studio\Version\PlatformSDK\adt-bundle-windows-x86-20131030\sdk.
Run dx with the --dex parameter, the --output parameter with the output path of the classes.dex file as its argument, and a space-separated list of paths to the JAR files that you want to include in the generated classes.dex file. For example:
dx --dex --output="classes.dex" "C:\Path\To\Library1.jar" "C:\Path\To\Library2.jar"
Note: You should create both a debug and a release version of your classes.dex file. The RAD Studio debugging features are only
available if the deployed classes.dex file contains the debug
versions of the included RAD Studio built-in Java libraries.
Deploying the `classes.dex` File
Warning: Follow these steps carefully. Android applications must always include a valid classes.dex file.
To configure your Android application to be deployed with your custom classes.dex file:
Select 'Project > Deployment' to open the Deployment Manager.
Uncheck the checkbox of the default classes.dex file.
Click the Add Files button and add your custom classes.dex file to the list of deployment files.
Change the Remote Path of your new entry to classes\.
Change the Platforms of your new entry to Android only.
See Troubleshooting in case if your app does not start after manipulations with the classes.dex file.
There is a library for Delphi XE7 for reading/scanning barcodes. This library was released in 2015 and is actively supported.
ZXing.Delphi - barcode scanning object Pascal library for Delphi XE7-Berlin.
So now if you want to read the barcode on a webcam, you don't need to tinker with .jar / .so files.
In my programming team we all use Delphi XE2 Professional. We just figured out that on different computers different numbers of VCL styles are available.
Where do VCL styles come from? Do I have to take care to move styles from one Delphi installation to another?
Q : Where do VCL styles come from?
A : The Vcl Styles files are part of the Delphi XE2 and XE3 versions, and are installed in two locations C:\Users\Public\Public Documents\RAD Studio\<n.n>\Styles and C:\Program Files (x86)\Embarcadero\RAD Studio\<n.n>\Redist\styles\vcl folders.
Also you the Vcl Styles files can be created from the scratch or customized, so maybe some of the machines contains custom Vcl Styles and that explain the different numbers of vsf files.
Q : Do I have to take care to move styles from one Delphi installation to another?
That's depends of how the Vcl Styles are added to the Delphi project. Basically exist 3 ways of add the Vcl styles to your project.
Using the Projects->Options->Application->Appearance Menu option. In this case a new entry by each style is added to the .dproj (Delphi project file) with the path to the style. After when you compile you project the styles referenced by the .dproj file are embedded as a resource.
Loading the styles manually (from a external file or resource) using the TStyleManager class.
Editing directly the .dproj file and adding a new entry called VCL_Custom_Styles in the <PropertyGroup Condition="'$(Base)'!=''"> Key.
So if you Delphi project is referencing the Vcl styles using the method 1 or 3, you will need copy the Vcl Styles between machines to avoid compilations problems if a Vcl style is missing.
Note : As recommendation you can create a style folder (and add that folder as part of you source control scheme) in your Delphi project location and here copy the vcl styles used by you Application, and then modify your code to load the styles using the method 2.