B4J Question [SOLVED] [ABMaterial] ABMGridBuilder and Java 11 or 14 issue

[Cableguy]

Hi all,

Despite the title, and even if the concerned code base is the ABMaterial Tool called "GridBuilder", this question is more about the "Build Stand Alone Package" feature.

ABMGridBuilder jar seems to not be compatible with Java11.0.1 nor with Java 14.0.1, as already discussed in this forum previously, when the packager was still a stand alone tool, not yet part of the IDE. The thread seemed to point to afound solution, consisting on changing a few lines in the packager source code, and that those changes would later be integrated into the new release of the tool. Later the tool bacame a part of the IDE.
I have searched the forum and downloaded the packager source code in order to verify and introduce, if needed, the needed changes, only to find that the changes were already there.
Still, my issue remained, and I turned to Alain, the creator of the ABM Framework, and he produced a package, using the IDE package tool, that in his computer works with both Java 11 and Java 14.

If I run the source code of the Grid Builder from the IDE, it works flawlessly, being it in debug as is release. BUT, the resulting jar only produces a blank form! Same behaviour I get with Alain's pakaged exe.

So... what can it be????

runing the grid builder from the IDE is far from an optimal solution.

Any hints?

 

[Erel]

What do you see when you run the debug.bat file?

 

[Cableguy]

 

[Erel]

Can you upload the compiled jar - the output that you get when you compile in release mode?

I assume that it runs fine in release mode, correct?

 

[Cableguy]

It does. I'm away from my pc for about 2h, will post the requested output then

 

[Cableguy]

I can't seem to attact the file, at 4.3Mb the forum claims its to be too large of a file!!!

 

[Cableguy]

Here is a link to the file:

File on MEGA

mega.nz

 

[Erel]

I've sent you an email with the full package created based on your jar. It works here. I guess that it will fail on your computer but please try it.

 

[Cableguy]

I will only be able to test it this afternoon, when I arrive from my day job

 

[Cableguy]

Has expected, it presents the exact same behaviour.

Can this be a antivirus (AVAST) issue?

 

[Erel]

Relevant: https://stackoverflow.com/questions...rexception-that-occurs-once-a-canvas-gets-too

I guess that this tool creates a very large canvas and you are hitting a limit. Hard to say why it doesn't happen when you run it from the IDE.

You can try to increase the max heap size by editing the batch file and adding this after java.exe: -Xms4096m -Xmx4096m

 

[Cableguy]

Hi EREL,

same thing... I even upped it to 6144 (6GB) but nothing changed.

 

[Erel]

I guess that the only solution is to see how the canvas is created and make it smaller.

 

[Cableguy]

After reading a bit of the stackoverflow thread you pointed, where it is stated that the issue may be in the canvas size, I decided to diveinto the code, searchng for the canvas defenitions.
The grid builder uses 4 canvas; one with 10k (!) height, and 3 with 1K height. Since I hardly ever be creating such a huge grid, I reduced theses sizes to abou half.
And guess what, it worked! The packaged exe works right out of the box.

[edit] you beat me for 3 seconds!!!

 

[Philip Chatzigeorgiadis]

After reading a bit of the stackoverflow thread you pointed, where it is stated that the issue may be in the canvas size, I decided to diveinto the code, searchng for the canvas defenitions.
The grid builder uses 4 canvas; one with 10k (!) height, and 3 with 1K height. Since I hardly ever be creating such a huge grid, I reduced theses sizes to abou half.
And guess what, it worked! The packaged exe works right out of the box.

[edit] you beat me for 3 seconds!!!

Can you please point to the code parts that need to be changed?
Thanks.
P.S. Perhaps it might be useful if AlwaysBusy could also make these changes permanent in future ABMaterial releases.

 

[Cableguy]

GridScrollPane.LoadLayout("GridCanvas", GridScrollPane.Width, 2000)

DevicesPane.LoadLayout("Devices")

PPane.LoadLayout("PCanvas", 150, 500)
TPane.LoadLayout("TCanvas", 150, 500)
DPane.LoadLayout("DCanvas", 150, 500)

 

[Cableguy]

P.S. Perhaps it might be useful if AlwaysBusy could also make these changes permanent in future ABMaterial releases.

I would suggest, if he could, recreate the tool without using the canvas in such huge way...