LMD VCL - General FAQ - Revision history

Rafael: /* Uninstallation */

2023-01-23T16:51:51Z

Uninstallation

← Older revision		Revision as of 18:51, 23 January 2023
Line 106:		Line 106:
	This issue is fixed in new LMD installers: Since LMD 2020.2 release a new SHA-2 signature was added to the installer which prevents this problem.<br><br>		This issue is fixed in new LMD installers: Since LMD 2020.2 release a new SHA-2 signature was added to the installer which prevents this problem.<br><br>
	To workaround this problem with installers till '''2020.1''' (including LMD/NG 2019, 2018 etc. installer):		To workaround this problem with installers till '''2020.1''' (including LMD/NG 2019, 2018 etc. installer):
	* Download updated uninstaller from here: '''~~http~~://files.lmd.de/downloads/utils/uninstall.zip'''		* Download updated uninstaller from here: '''https://files.lmd.de/downloads/utils/uninstall.zip'''
	* Copy UNWISE.EXE from the zip into your installation folder and replace the existing UNWISE.EXE file.		* Copy UNWISE.EXE from the zip into your installation folder and replace the existing UNWISE.EXE file.
	* After that Uninstaller works as expected.		* After that Uninstaller works as expected.

Rafael: /* Uninstallation */

2020-04-17T18:15:19Z

Uninstallation

← Older revision		Revision as of 20:15, 17 April 2020
Line 105:		Line 105:
	Issue is caused by SHA-1 signature of the uninstaller exe (UNWISE.EXE).<br>		Issue is caused by SHA-1 signature of the uninstaller exe (UNWISE.EXE).<br>
	This issue is fixed in new LMD installers: Since LMD 2020.2 release a new SHA-2 signature was added to the installer which prevents this problem.<br><br>		This issue is fixed in new LMD installers: Since LMD 2020.2 release a new SHA-2 signature was added to the installer which prevents this problem.<br><br>
	To workaround this problem with installers till '''2020.1''':		To workaround this problem with installers till '''2020.1''' (including LMD/NG 2019, 2018 etc. installer):
	* Download updated uninstaller from here: '''http://files.lmd.de/downloads/utils/uninstall.zip'''		* Download updated uninstaller from here: '''http://files.lmd.de/downloads/utils/uninstall.zip'''
	* Copy UNWISE.EXE from the zip into your installation folder and replace the existing UNWISE.EXE file.		* Copy UNWISE.EXE from the zip into your installation folder and replace the existing UNWISE.EXE file.

Rafael: /* Uninstallation */

2020-04-17T18:11:38Z

Uninstallation

← Older revision		Revision as of 20:11, 17 April 2020
Line 106:		Line 106:
	This issue is fixed in new LMD installers: Since LMD 2020.2 release a new SHA-2 signature was added to the installer which prevents this problem.<br><br>		This issue is fixed in new LMD installers: Since LMD 2020.2 release a new SHA-2 signature was added to the installer which prevents this problem.<br><br>
	To workaround this problem with installers till '''2020.1''':		To workaround this problem with installers till '''2020.1''':
	* Download updated uninstaller from here: ~~[[file:~~http://files.lmd.de/downloads/utils/uninstall.zip]]		* Download updated uninstaller from here: '''http://files.lmd.de/downloads/utils/uninstall.zip'''
	* Copy UNWISE.EXE from the zip into your installation folder and replace the existing UNWISE.EXE file.		* Copy UNWISE.EXE from the zip into your installation folder and replace the existing UNWISE.EXE file.
	* After that Uninstaller works as expected.		* After that Uninstaller works as expected.

Rafael: /* Uninstallation */

2020-04-17T18:08:13Z

Uninstallation

← Older revision		Revision as of 20:08, 17 April 2020
Line 106:		Line 106:
	This issue is fixed in new LMD installers: Since LMD 2020.2 release a new SHA-2 signature was added to the installer which prevents this problem.<br><br>		This issue is fixed in new LMD installers: Since LMD 2020.2 release a new SHA-2 signature was added to the installer which prevents this problem.<br><br>
	To workaround this problem with installers till '''2020.1''':		To workaround this problem with installers till '''2020.1''':
	* Download updated uninstaller from here: [[http://files.lmd.de/downloads/utils/~~uninstall.zip\|~~uninstall.zip]]		* Download updated uninstaller from here: [[file:http://files.lmd.de/downloads/utils/uninstall.zip]]
	* Copy UNWISE.EXE from the zip into your installation folder and replace the existing UNWISE.EXE file.		* Copy UNWISE.EXE from the zip into your installation folder and replace the existing UNWISE.EXE file.
	* After that Uninstaller works as expected.		* After that Uninstaller works as expected.
	~~{TOP}~~

	== IDE ==		== IDE ==

Rafael: /* Uninstallation */

2020-04-17T18:07:31Z

Uninstallation

← Older revision		Revision as of 20:07, 17 April 2020
Line 106:		Line 106:
	This issue is fixed in new LMD installers: Since LMD 2020.2 release a new SHA-2 signature was added to the installer which prevents this problem.<br><br>		This issue is fixed in new LMD installers: Since LMD 2020.2 release a new SHA-2 signature was added to the installer which prevents this problem.<br><br>
	To workaround this problem with installers till '''2020.1''':		To workaround this problem with installers till '''2020.1''':
	* Download updated uninstaller from here: [[~~uninstall.zip\|~~http://files.lmd.de/downloads/utils/uninstall.zip]]		* Download updated uninstaller from here: [[http://files.lmd.de/downloads/utils/uninstall.zip\|uninstall.zip]]
	* Copy UNWISE.EXE from the zip into your installation folder and replace the existing UNWISE.EXE file.		* Copy UNWISE.EXE from the zip into your installation folder and replace the existing UNWISE.EXE file.
	* After that Uninstaller works as expected.		* After that Uninstaller works as expected.

Rafael: /* Uninstallation */

2020-04-17T18:06:33Z

Uninstallation

← Older revision		Revision as of 20:06, 17 April 2020
Line 106:		Line 106:
	This issue is fixed in new LMD installers: Since LMD 2020.2 release a new SHA-2 signature was added to the installer which prevents this problem.<br><br>		This issue is fixed in new LMD installers: Since LMD 2020.2 release a new SHA-2 signature was added to the installer which prevents this problem.<br><br>
	To workaround this problem with installers till '''2020.1''':		To workaround this problem with installers till '''2020.1''':
	* Download updated uninstaller from here: [[http://files.lmd.de/downloads/utils/uninstall.zip]]		* Download updated uninstaller from here: [[uninstall.zip\|http://files.lmd.de/downloads/utils/uninstall.zip]]
	* Copy UNWISE.EXE from the zip into your installation folder and replace the existing UNWISE.EXE file.		* Copy UNWISE.EXE from the zip into your installation folder and replace the existing UNWISE.EXE file.
	* After that Uninstaller works as expected.		* After that Uninstaller works as expected.
	{{TOP}}		{TOP}

	== IDE ==		== IDE ==

Rafael: /* Uninstallation */

2020-04-17T18:05:49Z

Uninstallation

← Older revision		Revision as of 20:05, 17 April 2020
Line 103:		Line 103:
	After most recent operating system updates you might see following UAC dialog box:<br>		After most recent operating system updates you might see following UAC dialog box:<br>
	[[Image:uninstall.jpg\|UAC dialog box]]<br>		[[Image:uninstall.jpg\|UAC dialog box]]<br>
	Issue is caused by SHA-1 signature of the uninstaller exe (~~unwise~~.~~exe~~). Since LMD 2020.2 release a new SHA-2 signature was added which prevents this problem.<br>		Issue is caused by SHA-1 signature of the uninstaller exe (UNWISE.EXE).<br>
	To workaround this problem with installers till 2020.1:		This issue is fixed in new LMD installers: Since LMD 2020.2 release a new SHA-2 signature was added to the installer which prevents this problem.<br><br>
			To workaround this problem with installers till '''2020.1''':
	* Download updated uninstaller from here: [[http://files.lmd.de/downloads/utils/uninstall.zip]]		* Download updated uninstaller from here: [[http://files.lmd.de/downloads/utils/uninstall.zip]]
	* Copy UNWISE.EXE from the zip into your installation folder and replace the existing UNWISE.EXE file.		* Copy UNWISE.EXE from the zip into your installation folder and replace the existing UNWISE.EXE file.

Rafael at 18:04, 17 April 2020

2020-04-17T18:04:26Z

@@ Line 99: / Line 99: @@
 ** Browsing Path: Source files
 ** Debug DCU Path (optional): Path to DCU files with debug information. Not used with LMD VCL products.
 == IDE ==

Fduch at 12:12, 18 August 2017

2017-08-18T12:12:49Z

← Older revision		Revision as of 14:12, 18 August 2017
Line 5:		Line 5:
	=== CBuilder SpeedUp ===		=== CBuilder SpeedUp ===

	<syntaxhighlight lang="~~delphi~~">#include <oleidl.h>		<syntaxhighlight lang="cpp">#include <oleidl.h>
	#define NO_WIN32_LEAN_AND_MEAN </syntaxhighlight>NO_WIN32_LEAN_AND_MEAN <br>When this macro is defined, VCL.H does not define WIN32_LEAN_AND_MEAN. Default: OFF		#define NO_WIN32_LEAN_AND_MEAN </syntaxhighlight>NO_WIN32_LEAN_AND_MEAN <br>When this macro is defined, VCL.H does not define WIN32_LEAN_AND_MEAN. Default: OFF

Fduch at 12:12, 18 August 2017

2017-08-18T12:12:12Z

← Older revision		Revision as of 14:12, 18 August 2017
Line 5:		Line 5:
	=== CBuilder SpeedUp ===		=== CBuilder SpeedUp ===

	<~~pre class~~="~~brush:~~delphi">#include <oleidl.h>		<syntaxhighlight lang="delphi">#include <oleidl.h>
	#define NO_WIN32_LEAN_AND_MEAN </~~pre~~>NO_WIN32_LEAN_AND_MEAN <br>When this macro is defined, VCL.H does not define WIN32_LEAN_AND_MEAN. Default: OFF		#define NO_WIN32_LEAN_AND_MEAN </syntaxhighlight>NO_WIN32_LEAN_AND_MEAN <br>When this macro is defined, VCL.H does not define WIN32_LEAN_AND_MEAN. Default: OFF

	VCL_FULL<br>Same as NO_WIN32_LEAN_AND_MEAN (NOTE: This macro is for BCB v1.0 backward compatibility) Default: OFF		VCL_FULL<br>Same as NO_WIN32_LEAN_AND_MEAN (NOTE: This macro is for BCB v1.0 backward compatibility) Default: OFF
Line 165:		Line 165:

	To ''check'' for a flag, use code as follows: <br>		To ''check'' for a flag, use code as follows: <br>
	<~~pre class~~="~~brush:~~delphi">		<syntaxhighlight lang="delphi">
	if (foAutoCenter in MyLMDForm.Options) then DoWhatEver;		if (foAutoCenter in MyLMDForm.Options) then DoWhatEver;
	</~~pre~~>		</syntaxhighlight>
	This line of code tests whether foAutoCenter flag is currently set.		This line of code tests whether foAutoCenter flag is currently set.

	To ''enable'' or ''disable'' a specific flag, use following code:		To ''enable'' or ''disable'' a specific flag, use following code:
	<~~pre class~~="~~brush:~~delphi">		<syntaxhighlight lang="delphi">
	MyLMDForm.Options:=MyLMDForm.Options+[foAutoCenter];		MyLMDForm.Options:=MyLMDForm.Options+[foAutoCenter];
	</~~pre~~> or		</syntaxhighlight> or
	<~~pre class~~="~~brush:~~delphi">		<syntaxhighlight lang="delphi">
	MyLMDForm.Options:=MyLMDForm.Options-[foAutoCenter];		MyLMDForm.Options:=MyLMDForm.Options-[foAutoCenter];
	</~~pre~~>		</syntaxhighlight>

	=== Duplicate identifier during compilation ===		=== Duplicate identifier during compilation ===
Line 185:		Line 185:
	# Add lmdgraph before the type name of the corresponding type to ensure that correct type is used, e.g.		# Add lmdgraph before the type name of the corresponding type to ensure that correct type is used, e.g.

	<~~pre class~~="~~brush:~~delphi">LMDDBNImage1.Style := lmdgraph.sbNone;		<syntaxhighlight lang="delphi">LMDDBNImage1.Style := lmdgraph.sbNone;
	</~~pre~~>		</syntaxhighlight>

	=== E2134 Type 'TRect' has no type info ===		=== E2134 Type 'TRect' has no type info ===