Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » Elevate Web Builder Technical Support » Support Forums » Elevate Web Builder General » View Thread |
Messages 1 to 10 of 12 total |
DEFINE symbol remains effective when removed |
Wed, Nov 4 2015 2:52 AM | Permanent Link |
Michael Dreher | After compiling and executing (in the IDE) an application with a defined symbol, the symbol remains effective when it's commented out or removed from the code. Example:
--------------------------- {$DEFINE DEFINE_SOMETHING} // (0) procedure foobar; begin {$IFDEF DEFINE_SOMETHING} LogOutput('within the define section...'); // (1) {$ENDIF} end; initialization foobar; end. --------------------------- (1) is logged in the message window as expected. Now delete line (0), recompile and execute. (1) still is logged. The symbol remains effective until the a restart of the IDE. Michael Dreher |
Wed, Nov 4 2015 4:39 AM | Permanent Link |
Matthew Jones | Michael Dreher wrote:
> The symbol remains effective until the a restart of the IDE. I presume that this is the key. I expect the list of defines is not cleared at the start of compilation. More important, how come no one mentioned this new facility to me? 8-) What is really needed is a project option to be able to set at least one define, so that the code can be compiled appropriately. Command line support too. -- Matthew Jones |
Wed, Nov 4 2015 2:05 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Michael,
<< After compiling and executing (in the IDE) an application with a defined symbol, the symbol remains effective when it's commented out or removed from the code. >> Thanks, this is now fixed for 2.02 B5, which I'll be uploading this evening. Tim Young Elevate Software www.elevatesoft.com |
Sun, Jan 24 2016 11:39 AM | Permanent Link |
Gruetzmacher | was this fixed?
as with 2.04 it seems even {$IFDEF DESIGN} is not working ... Tim Young [Elevate Software] wrote: Michael, << After compiling and executing (in the IDE) an application with a defined symbol, the symbol remains effective when it's commented out or removed from the code. >> Thanks, this is now fixed for 2.02 B5, which I'll be uploading this evening. Tim Young Elevate Software www.elevatesoft.com |
Mon, Jan 25 2016 5:37 AM | Permanent Link |
Michael Dreher | Gruetzmacher wrote:
/// was this fixed? /// as with 2.04 it seems even /// {$IFDEF DESIGN} /// is not working ... I tracked this; the described error (defined symbol remaining effective once compiled) was fixed the next release and it still works in 2.04 Build 1. Can you provide a more complete code example of the problem? Michael Dreher |
Mon, Jan 25 2016 8:42 AM | Permanent Link |
Gruetzmacher | hello,
something like {$IFDEF DESIGN} LogOutput('Hallo'); {$ENDIF} does never get executed when running my project in the ide ... Michael Dreher wrote: Gruetzmacher wrote: /// was this fixed? /// as with 2.04 it seems even /// {$IFDEF DESIGN} /// is not working ... I tracked this; the described error (defined symbol remaining effective once compiled) was fixed the next release and it still works in 2.04 Build 1. Can you provide a more complete code example of the problem? Michael Dreher |
Mon, Jan 25 2016 9:45 AM | Permanent Link |
Raul Team Elevate | On 1/25/2016 8:42 AM, Gruetzmacher wrote:
> something like > {$IFDEF DESIGN} > LogOutput('Hallo'); > {$ENDIF} > > does never get executed when running my project in the ide ... I'm not sure DESIGN define is for actually running at app in IDE - i think it is for rendering it in IDE for the form designer (WYSIWYG aspects). When you run the app in DIE you would need all the code to run "normally" as it would do in browser (if you look at framework then DESIGN turns off lot of events and such). Raul |
Mon, Jan 25 2016 9:53 AM | Permanent Link |
Raul Team Elevate | On 11/4/2015 2:52 AM, Michael Dreher wrote:
> After compiling and executing (in the IDE) an application with a defined symbol, the symbol remains effective when it's commented out or removed from the code. Example: > --------------------------- > {$DEFINE DEFINE_SOMETHING} // (0) > > procedure foobar; > begin > {$IFDEF DEFINE_SOMETHING} > LogOutput('within the define section...'); // (1) > {$ENDIF} > end; > > initialization > foobar; > end. > --------------------------- > (1) is logged in the message window as expected. Now delete line (0), recompile and execute. (1) still is logged. The symbol remains effective until the a restart of the IDE. Not able to duplicate it here - 2.04 Build 1 using built-in web server. Once i commented out the "{$DEFINE... ", saved, recompiled and ran the project nothing was logged so works as expected. Raul |
Mon, Jan 25 2016 10:45 AM | Permanent Link |
Gruetzmacher | thank you Raul,
probably it was my wrong expectations. in delphi you have an ide compiler-symbol - that's what i thought 'DESIGN' would be Raul wrote: On 11/4/2015 2:52 AM, Michael Dreher wrote: > After compiling and executing (in the IDE) an application with a defined symbol, the symbol remains effective when it's commented out or removed from the code. Example: > --------------------------- > {$DEFINE DEFINE_SOMETHING} // (0) > > procedure foobar; > begin > {$IFDEF DEFINE_SOMETHING} > LogOutput('within the define section...'); // (1) > {$ENDIF} > end; > > initialization > foobar; > end. > --------------------------- > (1) is logged in the message window as expected. Now delete line (0), recompile and execute. (1) still is logged. The symbol remains effective until the a restart of the IDE. Not able to duplicate it here - 2.04 Build 1 using built-in web server. Once i commented out the "{$DEFINE... ", saved, recompiled and ran the project nothing was logged so works as expected. Raul |
Mon, Jan 25 2016 11:02 AM | Permanent Link |
Raul Team Elevate | On 1/25/2016 10:45 AM, Gruetzmacher wrote:
> thank you Raul, > probably it was my wrong expectations. in delphi you have an ide compiler-symbol - that's what i thought 'DESIGN' would be One can always ask Tim to include a future enhancement (if not already on the list) to allow for development time custom defines. Easiest would be to just ignore those during deploy step but more flexible would be "debug" vs "release" compile config option where you can configure the defines. Raul |
Page 1 of 2 | Next Page » | |
Jump to Page: 1 2 |
This web page was last updated on Thursday, March 28, 2024 at 06:05 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |