Servoy Forum

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

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.

Thanks Servoy !!

B.t.w.

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

Code: Select all

- 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,

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

Just remove them completely.

You where right Johan,

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

Thanks !!

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

Hello ,

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

Can you confirm this ?

lwjwillemsen wrote: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.

jcompagner wrote:

lwjwillemsen wrote: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 wrote:

lwjwillemsen wrote: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

jcompagner wrote:

jcompagner wrote:

lwjwillemsen wrote: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...

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,

lwjwillemsen wrote: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.

jcompagner wrote:

lwjwillemsen wrote: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

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.