Grid with "Row" labels vertical along the left, without the labels repeating for each record - just like the grid we have now, but reversing horiztonal and vertical - without manual coding.
We have Ajax & SQL power so an option to toggle search as you type behavior would be very powerful!
I would like a Search part as a completely separate Search Part that could then be coded... more »
How about a save & publish button (2 in 1) when working on a component. Will just make it easier when you want to do both and sometimes the save button doesn't register when you click to publish so you have to re-save then publish again.
It would be nice to see an auto suggest list (auto complete) feature added to the grid quick search text box like can be done in the full search grid part.
The Count(*) query is usually out of sight, out of mind, but checking my MySQL slow query log, I often find lots of these "SELECT Count(*) FROM..." queries.
These queries are created by Alpha... more »
I have tried overriding the Xbasic by creating new tmpl.groupBreaks.expression2=”second value” to no avail. I have also tried extending this with the Adjacency List Model, but this solution... more »
In addition the template should include more generic rule based properties (font size, row height as a function of font size, cell width based on field name or field length,... more »
But I find grids that appear and disappear have disadvantages:
1. They can be off-putting for new users.
2. They make it more difficult to create interfaces with more predictable appearance and behaviour.
I would therefore like the option to display an... more »
If you have a table or view w. many fields it is very difficult to find the field you want to add to the grid. We could really use an alphabetic sort option of available fields.
When checking the Export option on the properties tab there is no option for renaming the file something other than the system file name. This is possible with the action script. Maybe this is feature pack upgrade. It would also be great to have logic so that the grid can be name based on the search controls (and date created) used to generate the grid.
When this flag is checked, changing a grid field or having grid errors - then closing the grid will not pop up the 'You must undo edits' message and will gracefully close the grid.
An example of this:
When you have large datasets it makes it a lot easier for the user to scroll through a grid and see which datapoints are out of bounds visually. This is needed in the cases where the datapoints are not in... more »