| Extended property issues for 2.3 [message #1843922] |
Tue, 24 August 2021 14:03  |
 Arseniy Isakov
Messages: 118
Registered: May 2012 |
Senior Member |
|
|
Hi
I. have created two error simulation applications (See attachment)
1. VarUpdatedErrorEglEngine.java
If you run this file it will print
java.net.MalformedURLException1
2
3
Ignore "java.net.MalformedURLException" Dimitris mentions it will be fixed in 2.4.
But it should print
java.net.MalformedURLException1
2
2
2. ExtPropretyLostError
If you run this file it will print
java.net.MalformedURLException1
*8
*
Should be
java.net.MalformedURLException1
*8
*8
Actually second error connected with template "reset" method. You are cleaning cache and delete all extended properties
[Updated on: Tue, 24 August 2021 14:06] Report message to a moderator |
|
|
|
|
|
|
|
| Re: Extended property issues for 2.3 [message #1855800 is a reply to message #1855795] |
Thu, 03 November 2022 19:29  |
|
Hi Arseniy,
Apologies; this somehow fell through the cracks.
Regarding the first example, would it be possible to use EGL's higher-level API for parsing/loading templates as follows?
//VarUpdatedErrorEglEngine.java
...
EglTemplateFactoryModuleAdapter module = new EglTemplateFactoryModuleAdapter();
module.parse(Util.class.getResource("a1.egl").toURI());
module.execute();
...
//a2.egl
...
var templ : Template = TemplateFactory.load("b2.egl");
var buffer = templ.process();
...
In the second example, if b1.egl was not to have access to the variables of a1.egl, then var1="3" in b1.egl would throw an exception because var1 would be undefined. Replacing var var1="3" with var var1="3" does the trick.
I have attached a copy of the project with the proposed updates.
Thanks,
Dimitris
|
|
|
| Re: Extended property issues for 2.3 [message #1855871 is a reply to message #1855800] |
Tue, 08 November 2022 14:16 |
Arseniy Isakov
Messages: 118
Registered: May 2012 |
Senior Member |
|
|
Hi Dimitris
Regarding second issue I understood. So variables created in top module treated as Global variables. Variable created in child module is local.
Not sure if this is good solution. It gives compatibility problem with old version. You have pretty good mechanism to pass parameters to child template without globals
It is good to have compatibility switch for this
Thanks
Arseniy Isakov
[Updated on: Tue, 08 November 2022 16:25] Report message to a moderator |
|
|
|
| Re: Extended property issues for 2.3 [message #1856046 is a reply to message #1855874] |
Wed, 16 November 2022 19:52 |
|
Hi Arseniy,
Much as I'd like for EGL 2.x to be fully backwards compatible with 1.x, I'm afraid that we're unlikely to be able to allocate significant resources to this activity. If you can produce a fix for this issue that does not break the current EGL test suite, please submit a pull request and I'll review it as soon as possible.
Thanks,
Dimitris
|
|
|
Powered by
FUDForum. Page generated in 0.05348 seconds
] 
Search
Help
Register
Login
Home
