Servoy 6.1 rc 5

We are pleased to announce the immediate availability of Servoy 6.1 release candidate 5 (releaseNumber 1417).
If no issues are reported/found, this will be the last RC.

This version is available through the download option on the Servoy website and auto-update.
Always make a backup of your current Servoy installation (directory and database) before installing/upgrading.
To update a Servoy eclipse open Check for updates via help menu.

For Servoy 6.1 feature highlights see wiki

Known issues:

  1. The developer solution explorer view shows a couple of type duplicated

The issues fixed only in 6.1 or not yet released in other versions are:

Client Changes
[fix] SVY-2471 databaseManager.saveData(record/foundset) returns true even when onRecordInsert/Update triggers throw error
[fix] SVY-2531 Table scrolling background color
[fix] SVY-2525 Wicket Error in webclient when trying to remove a solution model form from the solution.
[fix] SVY-2509 getName() not working for scriptable form
[fix] SVY-2485 Web client list/table display jumping
[fix] SVY-2473 The onRender event no longer provides correct enabled and hasFocus information

Developer Changes
[enh] SVY-2079 Include left-hand side column in relation name during db relation reading
[fix] SVY-2503 Can’t set UUID flag to true and Sequence Type to UUID generator in 6.1 table editor
[fix] SVY-2491 Background of FormPopup is transparent in the webclient
[fix] SVY-2488 styleName changes are not working across extended forms
[fix] SVY-2465 application.setValueListItems expects different values from a JSDataSet in 6.1 than 5.2
[fix] SVY-2457 Erroneous warnings when a form method returns runtime form instances of the same type
[fix] SVY-2420 Tag inside for @param elements not working
[fix] SVY-2395 The JSDoc annotation {JSFoundSet<{col1: String, col2: Number}>}

Plugin Changes
[fix] SVY-2476 Allow rebind of DBTreeTable

Is web client support for the dialog plugin in the works? Such a major UI widget, seems strange an out-of-the-box version hasn’t been implemented yet.

Still having this problem in RC5

[attachment=0]Warnings.png[/attachment]

I have noticed that if I change the JSDoc to gsfwk_nav_TblMntCntr I dont get those warnings. Seems that inherited properties are not shown.

In the release note

JSDoc
Added ‘nls’ option to the JSDoc @SuppressWarning tag to suppress all builder markers related to non-externalized text within one method
Added ‘unused’ option to the JSDoc @SuppressWarning tag to suppress builder markers related to unused private variables

but when I at the suppressWarning,

[attachment=0]unused.png[/attachment]

the warning is still there.

Regards,

Peter

Hi Peter,

You forgot the quotes, try ‘unused’ and it will work.

Greetings,
Omar

Ehm, I was too quick with my reply. The quotes are necessary but indeed, the warning doesn’t dissapear…

It does work however if you place it inline directly above each unused variable like this:

/** @SuppressWarnings('unused') */
var test;

I suppose that way you can differentiate between variables that are intentionally unused and those that are not.

Show-stopper level bug filed:

https://support.servoy.com/browse/SVY-2567

Another critical issue which we are experiencing with RC5 - https://support.servoy.com/browse/SVY-2571

jasantana:
Still having this problem in RC5

I have noticed that if I change the JSDoc to gsfwk_nav_TblMntCntr I dont get those warnings. Seems that inherited properties are not shown.

i can’t reproduce this, i have this code:

	/** @type {RuntimeForm<subForm>} */
	var form = forms["supForm"];
	form.subFormVariable = "test";
	form.superFormVar =  "test"

where i have subForm and superForm (subForm extending superForm)

Do you have any module structure? where the sub and super form are in different modules or the globals function where you access them is in a different module?

david:
Show-stopper level bug filed:

https://support.servoy.com/browse/SVY-2567

Thanks for the fast turn around on this one!

3rd party tester identified a new issue of some importance (annoying type one):

https://support.servoy.com/browse/SVY-2588

jcompagner:

jasantana:
Still having this problem in RC5

I have noticed that if I change the JSDoc to gsfwk_nav_TblMntCntr I dont get those warnings. Seems that inherited properties are not shown.

i can’t reproduce this, i have this code:

	/** @type {RuntimeForm<subForm>} */
var form = forms["supForm"];
form.subFormVariable = "test";
form.superFormVar =  "test"



where i have subForm and superForm (subForm extending superForm)

Do you have any module structure? where the sub and super form are in different modules or the globals function where you access them is in a different module?

Johan thanks for your reply. Here you have a test solution. Please, check the global method createForm.

UPDATE

Johan I have updated the solution because I see what I think that is a bug. Run SuperForm and You will see you have a button to add tabs. Click on it and 3 tabs will be added to the tabPanel. You can move thru with the buttons or with the servoy tabs. At the botton of the form you will see 3 buttons to delete tabs. Use them and everything works fine.
Now try to do the sameafter changing the tabOrientation property of the tabPanel to HIDE. You will see the problem.

Deleting tabs when the tabOrientation property is HIDE doesn´t work properly.

Thanks.
[attachment=0]Tests.servoy[/attachment]

Tests.servoy (5.44 KB)

can you create a case (or 2 cases if these are really 2 separate things) with that solution?
else it will be lost i am afraid.

jcompagner:
can you create a case (or 2 cases if these are really 2 separate things) with that solution?
else it will be lost i am afraid.

Done. Cases: https://support.servoy.com/browse/SVY-2601 and https://support.servoy.com/browse/SVY-2600

What about the deprecated method like

getFormMethod
newCalculation
newFormMethod

is there any documentations or something to change this methods with others?

DEK4:
What about the deprecated method

If you press “ALT” and then hover the call to the deprecated method, it shows in the tooltip which method you should use now.

Thanks a lot!! :D