ZylAppCommunicator 1.23 for D10.2 Tokyo

ZylAppCommunicator 1.23 for D10.2 Tokyo
ZylAppCommunicator 1.23 for D10.2 Tokyo | 25 kB

ZylAppCommunicator is a Delphi & C++Builder component which lets you to communicate between one or more applications which are running on the same computer. Use ZylAppCommunicator if you want to easily communicate between your applications.

 

Supported Operating Systems:
Windows 95/98/Me/NT/2000/XP/Server2003/Vista/Server2008/7/8/Server2012/10
Available for: Delphi 10.2 (Win32 & Win64), Delphi 10.1 (Win32 & Win64), Delphi 10 (Win32 & Win64), Delphi XE8 (Win32 & Win64), Delphi XE7 (Win32 & Win64), Delphi XE6 (Win32 & Win64), Delphi XE5 (Win32 & Win64), Delphi XE4 (Win32 & Win64), Delphi XE3 (Win32 & Win64), Delphi XE2 (Win32 & Win64), Delphi XE, Delphi 2010, Delphi 2009, Delphi 2007, Delphi 2006, Delphi 2005, Delphi 7, Delphi 6, Delphi 5, Delphi 4, C++Builder 10.1 (Win32 & Win64), C++Builder 10 (Win32 & Win64), C++Builder XE8 (Win32 & Win64), C++Builder XE7, C++Builder XE6, C++Builder XE5, C++Builder XE4, C++Builder XE3, C++Builder XE2, C++Builder XE, C++Builder 2010, C++Builder 2009, C++Builder 2007, C++Builder 2006, C++Builder 6, Turbo Delphi, Turbo C++
Remarks:
– The Delphi 2006 version is fully compatible with Turbo Delphi
– The C++Builder 2006 version is fully compatible with Turbo C++
– No Delphi for .NET support
Limitations:
– Windows Vista/2008/7/8/2012/10 limitations:
1. cannot be used for communication between applications with different isolation level (ex: application with service).
2. applications running at normal privilege levels are not allowed to communicate with applications running at higher privilege levels.
If your application needs to communicate with an application with higher privilege level, you have to do the following:
-the uiAccess flag must be set to true in your application’s manifest.
-your application must be digitally signed.
-your application must reside in a trusted location (e.g.; Program Files), otherwise the uiAccess flag is ignored.
Installation:
If you have a previous version of the component installed, you must remove it completely before installing this version. To remove a previous installation, proceed as follows:
-Start the IDE, open the packages page by selecting Component – Install Packages
-Select ZylAppCommunicatorPack package in the list and click the Remove button
-Open Tools – Environment Options – Library and remove the library path pointing to ZylAppCommunicator folder
-Close the IDE
-Browse to the folder where your bpl and dcp files are located (default is $(DELPHI)\Projects\Bpl for Delphi, $(BCB)\Projects\Bpl for C++ Builder). -Delete all of the files related to ZylAppCommunicator
-Delete or rename the top folder where ZylAppCommunicator is installed
-Start regedit (click Start – Run, type “regedit.exe” and hit Enter). Open the key HKEY_CURRENT_USER\Software\Borland\\\Palette and delete all name/value items in the list related to ZylAppCommunicator. ( is either “Delphi” or “C++Builder”, is the IDE version you have installed)
-Unzip the zip file and open the ZyAppComunicatorPack.dpk file in Delphi (ZylSerialPortPack.bpk file in C++Builder), compile and install it
and add to Tools/Environment Options/Library (in older Delphi/C++Builder menu) or Tools/Options/Delphi Options/Library/Library Path (in newer Delhi menu) or Tools/Options/C++ Options/Paths and Directories/Library Path & Include Path (in newer C++Builder menu, in C++Builder 10 or later, set them also for the classic compiler) the path of the installation (where the ZyAppComunicator.dcu file is located). The component will be added to the “Zyl Soft” tab of the component palette. After you have the component on your component palette, you can drag and drop it to any form, where you can set its properties by the Object Inspector and you can write event handlers selecting the Events tab of the Object Inspector and double clicking the preferred event.
If you still have problems in C++Builder, running an application, which contains the component, then open the project and in C++Builder menu, Project/Options/Packages and uncheck “Build with runtime packages”.
-It is indicated to use this component with “Stop on Delphi exception” option deactivated. You can do this from Delphi / C++Builder menu, Tools/Debugger Options/Language Exceptions/Stop on Delphi exceptions in older versions or Tools/Options/Debugger Options/Embarcadero Debuggers/Language Exceptions/Notify on language exceptions in newer versions, otherwise you will have a break at all the handled exceptions.
Help file:
If you can’t open the help file:
-right-click on the help.chm file to get the properties
-on the bottom it says: “This file came form another computer….”
-push “Unblock” next to this text
-now the help.chm files opens as all other help files
What’s new:
– support for Delphi/C++Builder 10.2 Tokyo
– support for Delphi/C++Builder 10.1 Berlin
– support for Delphi/C++Builder 10 Seattle
– C++Builder 64-bit support
– support for Delphi/C++Builder XE8
– support for Delphi/C++Builder XE7
– support for Delphi/C++Builder XE6
– support for Delphi/C++Builder XE5
– support for Delphi/C++Builder XE4
– support for Delphi/C++Builder XE3
– Windows 64-bit support

 

ZylAppCommunicator, communicate, applications, between, which, computer, easily, running, Tokyo, Builder, Delphi, component, Builder, Delphi, support, Options, component, ZylAppCommunicator, Tools, Library, where, files, Start, exceptions, remove, version, click, newer, folder, installed, Environment, located

http://pasted.co/e7ff4a24

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s