Servoy 3.5.8

We are pleased announce the immediate availability of Servoy 3.5.8

Make a backup of your current Servoy installation (directory and database) before installing.

This version will be available shortly through auto update for users of 3.5 versions (check via help menu → check for new version)

Changes:
[enh] case 143120: Add record exception.getSQLParameters() function
[enh] case 156441: Combobox in readonly mode
[enh] case 67428: sample code of getElementType should give you all the possible solutions

[fix] case 154859: tab through a TEXT_AREA doesn’t work anymore in 3.5.7
[fix] case 152336: labels DO wrap in webclient
[fix] case 154845: Attaching onRecordEditStart method on ListView requires extra click
[fix] case 154467: Tableview/Portal header height grows when sort direction triangle is shown
[fix] case 153395: focusFirstField does not work in listview
[fix] case 147623: webclient dropdown calendar month name in FR locale special chars display problem
[fix] case 155507: Tableview when searching uses relation without reason
[fix] case 155451: Tooltip find help text not in i18n
[fix] case 156454: Schema name not honored when creating tables with system user
[fix] case 137555: webclient shutdown drops error in log: No foundset in form found!
[fix] case 99265 : Problem with update of unstored calc fields in webclient
[fix] case 157038: List values show the wrong value in Webclient
[fix] case 157727: Miss behavior is web client for date fields
[fix] case 159005: dataset.sort(4, false) doesnt work in 3.5.7
[fix] case 159004: problem with editable combobox
[fix] case 157726: Strange solution export message in 3.5.7
[fix] case 157761: Readonly Fields issue
[fix] case 159614: non-editable field becoming editable by setting it to readonly
[fix] case 119114: Non-ASCII characters messed up in headless client
[fix] case 158697: onDataChange not fired anymore after find/search
[fix] case 156715: Two level showFormInDialog() not working in web client
[fix] case 160770: Error message due to missing parameter in SQL query does not include SQL query
[fix] case 165169: Page Setup Issue
[fix] case 165696: |U format in field causes beep
[fix] case 166410: combobox/valuelists problem in 3.5.7
[fix] case 165980: Problem with number fields
[fix] case 138366: date field input validation issues, when trying to revert to old value
[fix] case 154469: Portal transparent property has no effect
[fix] case 166841: Webclient: rapidly blinking tooltips
[fix] case 165126: servoy client on thin client running on a terminal server won’t work
[fix] case 149560: a small problem with find in web client
[fix] case 87676: the useAjax checkbox per solution is only evaluated for the first solution opened per browser session
[fix] case 75966: Value lists show row of current record in first line in webclient
[fix] case 169954: Related records in tab are not shown with databaseManager.setCreateEmptyFormFoundsets()
[fix] case 139696: wrong developer ToolTip of application.closeFormIndialog()
[fix] case 174280: Blob problem if a table has multiple blob colums with near similar names
[fix] case 169882: plugins.http.getPageData does not use browser proxy
[fix] case 174418: image plugin doesn’t handle CMYK based TIFF’s wel if at all
[fix] case 101363: previews and next button of internet explorer does not work in webclient
[fix] case 126563: Webclient: double records created in DB when firing a method by pressing a button once, where script only creates a new record once
[fix] case 108602: Webclient: Calculated field content sometimes disappear
[fix] case 52637 : Webclient: TableViews don’t fit anymore
[fix] case 97979 : body tag with attributes will cause web exception (invalid html)
[fix] case 177070: HTML is not rendered well in the web client
[fix] case 69098 : Type-Ahead, SINGLE-click selection
[fix] case 178187: addTableFilterParam not working from global method onOpen
[fix] case 177449: problem with escape key in find mode (hangs solution)
[fix] case 181638: Tooltips that utilize display tags do not work
[fix] case 177625: problems using escape-key to cancel search in different views
[fix] case 185291: WebClient tableviews are depending on a timer to be rendered.
[fix] case 185224: i18n dialog very slow
[fix] case 185741: bottom navigator not shown on iphone & Safari on MAC
[fix] case 155374: DBTreeTableView bean GUI glitches
[fix] case 179918: .setChildSortDataprovider() on DbTreeView bean doesn’t work

Previous release
viewtopic.php?f=16&t=11025

Lots of great fixes here - thanks guys. But… all my media fields no longer display images in web client. Instead I can see the field name as an apparently editable field (you can actually edit it) on top of the empty media field. Same results with Safari, Firefox, Camino, all in OS X. Can anyone else confirm?

The media field problem is fixed for the next 3.5.x (and 4.1.x) releases
If this is causing a problem in your solution with 3.5.8 please contact us to get an intermediate build.

Thanks for all the bugfixes !!

One question : Has something changed in the size or font of labels ?

I have labels in 3.5.7 like “Opdrachtnemer” and they display fine.
in 3.5.8 some labels now do not display complete and end in … like “Opdrachtnem…”

I have to increase the horizontal size by 1 or 2 to display them correctly ???

Regards,

Hans

hans, do you see a difference in the font if you compare?
i guess you are talking about the smart client yes? Not the web?

Hi Johan,

Yes it is Smartclient.

I will upload document with 2 screenshots.

Hans

labeliss.doc (178 KB)

[fix] case 179918: .setChildSortDataprovider() on DbTreeView bean doesn’t work

I now see in some cases that it did work before and now it doesn’t.
I’ll try to find out if I can see in what situation this happens.

hans,

do you use stylesheets? and do you have margin settings in it?

Yes we use stylesheets (same for 3.5.7 as for 3.5.8

label
{
background-color: #f5f0bd;
color: #00438c;
border-style: TitledBorder;
font: bold 11pt Tahoma;
border-top-color: #f5e6bd;
border-right-color: #f5e6bd;
border-bottom-color: #ffffff;
border-left-color: #f5e6bd;
margin: 1px 1px 1px 1px;
}

Regards,

Hans

and if you play with that margin settings?

Hi Johan,

Setting the margins to 0 seems to solve the issue.

So there was a change in the way margins are handled ??

Regards,

Hans

the childsort dataprovider should be in the parent foundset

margins are now applied, they where ignored before. that is fixed

It looks indeed that

[fix] case 179918: .setChildSortDataprovider() on DbTreeView bean doesn’t work

should not have [fix], but [new bug] :wink: because it worked before and now it doesn’t anymore.
See the screenshot. The numbers after the description show the sortorder. As you can see on the first level the sortorder is correct, but on the second level it isn’t, while it was correct before.

I’ve put it in a small solution, which will be uploaded into the supportsystem.

var _foundset = databaseManager.getFoundSet('globis_framework', 'sec_user_menu')	
	
_foundset.clear();
_foundset.loadRecords(_query, ['R', globals.owner_id, globals.user_id])
_foundset.sort('parent_menu_id asc, menuitem_sequence asc');

controller.loadRecords(_foundset)

var _binding = elements.dbtreeview.createBinding('globis_framework', 'sec_user_menu')

_binding.setChildSortDataprovider('menuitem_sequence asc')
_binding.setNRelationName('sec_user_menu_to_sec_user_menu$parent_menu_id')
_binding.setTextDataprovider('display_description')

elements.dbtreeview.transparent = 1
elements.dbtreeview.addRoots(_foundset)

_binding.setChildSortDataprovider(‘menuitem_sequence asc’) is wrong,
the param must be a column name / calculation that contains the order string

Hi martinh

I run in the same problem. The rule has changed. Here’s the info from Servoy-support:

hi,

childsort dataprovider must be a field/calc in the parent foundset, as
different parent nodes, can have different sort on theier children,
but the value returned by the dataprovider, must be a field in the
child foundset

regards,
Gabi

I’ve changed the logic. Now it works on my side.

Cheers,
hp

Gabi,

Thanks for the info.
It must have been changed since version 3.5.7 because before I used it like I showed in the sample and that worked.
I made the change that you suggested and indeed the sort order is correct now

Thx

Martin

hi to all,

setChildSortDataprovider did not changed, but there was a bug
in the prev version, that if it was not a self join relation, the sort didn’t worked
on the children

regards,
Gabi