Attached to this post you will find version 5.2.7.685 of the frameworks.
The sampleuse_navigation file with all the modules and data, this is best for new installs. The svy_navigation file includes all the modules but no data, this one is for updating your installation.
This is the list of all the main changes/enhancements:
*new Login form stays centralized when resizing the form
*new User can select a default table view
*new Lookup columns can have variable width
*new Ability to set the show/new button of lookup windows
*new Ability to filter the foundset of lookup windows
*new Properties to set the window size and if you want to restore it every session
*new Flexibel views
*new Extra view: detail view without tabs
*fix In edit mode not all fields on tabpannels change color correctly
*fix Security of normal users did not look at program settings
*fix Global report menu was not working anymore
*fix The splitpane position of the user was not restored properly
*fix Toggle view was not working when using multiple relations
*fix Compare view should also work withs forms without datasource
*fix Let svy_nav_checkRequiredFields work with SPLITPANES
*fix Bug in svy_mod_dialog, error when showing a valuelist dialog twice
This will probably be the last framework version for Servoy 5, the next version will be in Servoy 6!
I am sorry about the error, that because there are new properties.
After the error you can use control + 1 to open the navigator.
Then use the refresh button at the properties tab to create non existing properties.
See image:[attachment=0]properties.png[/attachment]
If you want to work with the 4 views, first remove all the properties with “template” in them and then press the recreate properties button.
Then the program still work with the 3 views so you have to go to the program tab and refresh all the programs.
See image:
[attachment=0]program.png[/attachment]
The first error when the application starts now is ok. I have opened the framework configuration and i have refreshed the properties and the program’s page.
Now i have saved the column width of a lookup window and the first time i have opened the windows it was all ok, then the width is back to the original width and i can set it like i want…Then the lookup window has always the scrollbars visible even if it is not necessary…
Another little question. Is there a way to make id fields in the lookup visible with format without the “.” separator (9999999 instead of 999.999)
It was the 5.2.7.685 version. There might be a few small changes that also will be in the next version of the frameworks but I don’t believe there where big differences. What did you see that you are missing in the 5.2.7.685 version?
logicimpresa:
when I refresh the Navigation Configurator raise an error.
I tested this but I don’t have a error. Are there specific step you do before you get the error?
logicimpresa:
Another question: how to delete the Template Properties ?
Open the navigator configurator (with ctrl+1)
Go to the ‘properties’ tab
Click on ‘name’ to sort
Select a property that starts with ‘template_’ and press the delete button.
[attachment=0]property_delete.png[/attachment]
Hi Sanneke,
The steps for raise error in Navigation Configurator are:
Open the form with Ctrl+1
Click the refresh button immediatly (Refresh Nav Object)
Servoy Log Error response:
Stale form(s) detected, form(s) were altered by the solution model without destroying them first
The form(s) that are stale (can also be a parent form if form inheritance is used) are:
Form name:‘svy_nav_fr_buttonbar_viewer’ with instances: [svy_nav_fr_buttonbar_viewer]
at D:\servoy_apps\svy_nav_navigation\globals.js:4036
Form name:‘svy_nav_fr_buttonbar_browser’ with instances: [svy_nav_fr_buttonbar_browser]
at D:\servoy_apps\svy_nav_navigation\globals.js:4025
I use Windows 7 Ultimate with last release of Servoy 5
Hans Nieuwenhuis:
Hi Sanneke,
But, the 4 view buttons ( list, detail view, ., …) show the tooltip on the first tap
and execute there method on the second tap.
regards,
Hi Hans,
This is one of the small items I did change, if you replace the attached method it should work fine.
Hi Sanneke,
Are you keeping the linked solutions at the beginning of this thread current (i.e. with all the here mentioned fixes) , or do we stil need to incorporate them all by our own?
