Servoy 5.1 beta 3

Jan_Blok · January 26, 2010, 2:27pm

We are pleased to announce the immediate availability of Servoy 5.1 beta 3

This version is available through auto update only, always make a backup of your current Servoy installation (directory and database) before upgrading.
To update eclipse open, Window → Preferences (update sites), change:
-The servoy update site in eclipse to: http://www.servoy.com/developer/5xx_updates/beta
-Disable both eclipse.org update-sites for now, since there is a problem at the eclipse side!

Client changes:
[fix] 251812 page counter falls off the screen when showing formINDialog
[fix] 268573 showForm of an solutionModel cloned form doesn’t fire event methods
[fix] 268777 recreateUI doesn’t recreate tableviews correctly
[fix] 260006 When using the default Servoy Sort dialog, if the user selects the Cancel button, the current sort of the foundset is cleared instead of leaving it as it is.

-Splitpane issues:
[fix] 267562 minWidth/minHeight settings required on ‘splitpane element’
[fix] 267555 New solution model values for orientation property to make panel a splitpane
[fix] 267574 ‘splitpane’ element needs a resizeWeight setting

Developer changes:
[fix] 262459 Servoy hangs on newRecord() in developer after switchServer
[fix] 268225 ‘Set to Default’ option in context menu on Property Editor for the ScrollBar property is not available

Plugin changes:
[fix] 268186 The serialize plugin should not try to serialize functions
[fix] 268041 MultiSelect fileupload dialog in WC does not grow, after selecting multiple files, meaning you have to scroll inside the dialog to get to the upload button

jcompagner · January 26, 2010, 4:34pm

there is a problem with the file plugin in b3 in serclipse (server/smart client works fine)

you can download the fix:

http://downloads.servoy.com/downloads/b … n/file.jar

and drop in in the application_server/plugins dir.

Hans_Nieuwenhuis · January 26, 2010, 5:06pm

Thanks Servoy !!

B.t.w.

In the log file there are errors concerning the 4 plugins thet where replaced :

- Error occured trying to load: F:\Program Files\servoy5_ibis\application_server\plugins\popupmenu.jar, error: error in opening zip file
2010-01-26 17:59:35,823 ERROR [main] com.servoy.j2db.util.Debug - Error occured trying to load: F:\Program Files\servoy5_ibis\application_server\plugins\batchprintjob.jar, error: error in opening zip file
2010-01-26 17:59:36,057 ERROR [main] com.servoy.j2db.util.Debug - Error occured trying to load: F:\Program Files\servoy5_ibis\application_server\plugins\menubar.jar, error: error in opening zip file
2010-01-26 17:59:36,057 ERROR [main] com.servoy.j2db.util.Debug - Error occured trying to load: F:\Program Files\servoy5_ibis\application_server\plugins\kioskmode.jar, error: error in opening zip file

Regards,

jcompagner · January 26, 2010, 5:07pm

i guess if you look into the plugin dir you will see those files as 0 byte files?

Just remove them completely.

Hans_Nieuwenhuis · January 26, 2010, 5:32pm

You where right Johan,

They where 0 bytes, I removed them and the log entries are gone.

Thanks !!

martinh · January 27, 2010, 11:38am

Is the 5.1 release the next public release or will there be also a 5.0.2 release?

lwjwillemsen · January 27, 2010, 12:46pm

Hello ,

In b3 the saving of the global method info in the valuelist-editor seems to be broken…

Can you confirm this ?

jcompagner · January 27, 2010, 12:54pm

lwjwillemsen:
Hello ,

In b3 the saving of the global method info in the valuelist-editor seems to be broken…

Can you confirm this ?

yes in certain situations it behaves strange, i encountered this before, but couldnt reproduce it anymore,
Now i seem to found a situation that the name of the global method will disappear at the moment you save it.

lwjwillemsen · January 27, 2010, 1:06pm

jcompagner:

lwjwillemsen:
Hello ,

In b3 the saving of the global method info in the valuelist-editor seems to be broken…

Can you confirm this ?

yes in certain situations it behaves strange, i encountered this before, but couldnt reproduce it anymore,
Now i seem to found a situation that the name of the global method will disappear at the moment you save it.

Hi Johan,

Sounds scary , but I think you will find a solution (as always)…

jcompagner · January 27, 2010, 1:52pm

jcompagner:

lwjwillemsen:
Hello ,

In b3 the saving of the global method info in the valuelist-editor seems to be broken…

Can you confirm this ?

yes in certain situations it behaves strange, i encountered this before, but couldnt reproduce it anymore,
Now i seem to found a situation that the name of the global method will disappear at the moment you save it.

found the problem and fixed it for the next build

lwjwillemsen · January 27, 2010, 2:59pm

jcompagner:

jcompagner:

lwjwillemsen:
Hello ,

In b3 the saving of the global method info in the valuelist-editor seems to be broken…

Can you confirm this ?

yes in certain situations it behaves strange, i encountered this before, but couldnt reproduce it anymore,
Now i seem to found a situation that the name of the global method will disappear at the moment you save it.

found the problem and fixed it for the next build

Thanks, Johan !

For now I use the good old text editor on the .val files…

lwjwillemsen · January 29, 2010, 7:38am

Hi ,

I’ve noticed that the foundsetUpdater.performUpdate() starts the updating at the selectedIndex of the involved foundset !
Is this by design or belongs it to the same selectedIndex issues I saw in the past days…

For now I issue setSelectedIndex(1) before the performUpdate() and all records in the foundset are nicely updated…

Regards,

jcompagner · January 29, 2010, 9:16am

lwjwillemsen:
Hi ,

I’ve noticed that the foundsetUpdater.performUpdate() starts the updating at the selectedIndex of the involved foundset !
Is this by design or belongs it to the same selectedIndex issues I saw in the past days…

For now I issue setSelectedIndex(1) before the performUpdate() and all records in the foundset are nicely updated…

Regards,

thats by design, it does that already for quite some time.

lwjwillemsen · January 29, 2010, 9:54am

jcompagner:

lwjwillemsen:
Hi ,

I’ve noticed that the foundsetUpdater.performUpdate() starts the updating at the selectedIndex of the involved foundset !
Is this by design or belongs it to the same selectedIndex issues I saw in the past days…

For now I issue setSelectedIndex(1) before the performUpdate() and all records in the foundset are nicely updated…

Regards,

thats by design, it does that already for quite some time.

Hello Johan,

As this not to expect behaviour (updating starts at selectedIndex) is not stated in the Servoy documentation I rate it as a bug…

Mail it to Paul for a Wiki update ?

Regards

jcompagner · January 29, 2010, 10:07am

the sample of update method does tell you that already:

//3) safely loop through foundset (starts with selected row)
controller.setSelectedIndex(1)
var count = 0
var fsUpdater = databaseManager.getFoundSetUpdater(foundset)
while(fsUpdater.next())
{
fsUpdater.setColumn(‘my_flag’,count++)
}

will see if i can improve the doc itself a bit.

lwjwillemsen · January 29, 2010, 10:23am

jcompagner:
the sample of update method does tell you that already:

//3) safely loop through foundset (starts with selected row)
controller.setSelectedIndex(1)
var count = 0
var fsUpdater = databaseManager.getFoundSetUpdater(foundset)
while(fsUpdater.next())
{
fsUpdater.setColumn(‘my_flag’,count++)
}

will see if i can improve the doc itself a bit.

Johan,

From the Servoy Wiki :

//There are 3 types of possible use with the foundset updater
//1) update entire foundset
var fsUpdater = databaseManager.getFoundSetUpdater(foundset)
fsUpdater.setColumn(‘customer_type’,1)
fsUpdater.setColumn(‘my_flag’,0)
fsUpdater.performUpdate()

I am using (the very nice) option 1 in the hope that Servoy translates that into 1 SQL update statement…
You can see here is no need to set the selectedIndex !

jcompagner · January 29, 2010, 10:36am

that first one doesnt use the selected index.
Because that just generate 1 sql statement that updates the whole foundset at once.
Are you sure that you use it like that? What does the performance tab tell you when you clear it, then run it?
What kind of sql statements are fired?

lwjwillemsen · January 29, 2010, 1:06pm

jcompagner:
that first one doesnt use the selected index.
Because that just generate 1 sql statement that updates the whole foundset at once.
Are you sure that you use it like that? What does the performance tab tell you when you clear it, then run it?
What kind of sql statements are fired?

Hi Johan,

My code :
var _fs = _fs0.duplicateFoundSet() // _fs0 is initial foundset
// _fs.setSelectedIndex(1)
var _fsu = databaseManager.getFoundSetUpdater(_fs)
_fsu.setColumn(_field, _value)
var _ok =_fsu.performUpdate()
if (_ok) {
databaseManager.saveData()
}

In performance tab appl.server :
00:00:016 4 00:00:002 Update update glb_supplier set log_modification_dt=?, glb_currency_id=? where glb_supplier_id = ? and owner_id in (?, ?)

So Servoy goes into foundset iterating mode in stead of 1 update statement for the whole foundset. In my test I have 6 records in the foundset and the selectedIndex is 2 (6-2=4 updatestatements)

I think the complete foundset updater does not work as described…

jcompagner · January 29, 2010, 3:22pm

the value you put in is just a string or number right? (not an array with values)

also the foundset isnt build on a table that has tracking enabled?

lwjwillemsen · January 29, 2010, 3:55pm

jcompagner:
the value you put in is just a string or number right? (not an array with values)

also the foundset isnt build on a table that has tracking enabled?

Johan,

Value is (just) an integer value.
Tracking is enabled on this foundset.

Topic		Replies	Views
Servoy 5.1 beta 2 Classic Servoy	18	32513	January 26, 2010
Servoy 5.1 beta 1 Classic Servoy	17	35579	January 20, 2010
Servoy 5.1 rc 1 Classic Servoy	46	137862	March 9, 2010
Servoy 5.1 Final Classic Servoy	22	40725	April 27, 2010
Servoy 5.1 rc 2 Classic Servoy	4	12094	February 5, 2010

Servoy 5.1 beta 3

Related topics