Re: O$: adding column to complex grid

Hi Doug,

Excuse my language, I’ll try to be more careful and not use the CG word.
I blame Hollywood for desensitising me, really.

—— the following email is rated PG13 for some profane Omnis language
——

I agree with you on Headed Lists. We use them 99% of the time as well
and it looks like we can do a whole lot more with them. Thanks for the
tips, I’ll have to look into moving columns and saving the list’s layout
for each user.

But there are those few cases where it makes sense to use a C-Grid
instead. I just never realised it was so difficult to add a column in
the middle. I figured I was overlooking something, but guess not. I’ll
drop a little enhancement request with Omnis Support Germany, see if I
can stir the pot.

Cheers,

Nick

On 7 Aug 2017, at 16:06, Doug Easterbrook wrote:

> hi nick.
>
> you said two dirty words as far as your question went. Complex Grid.
>
>
> so be sure, complex grids are useful in any application and we have 4
> places that we use them. They are fantastic for a complicated multi
> line display with large icons and entry fields — however the
> limitation about them is .. changing them involved work.
>
>
> on the other hand, a headed list box offers a whole lot of good so we
> use it in about 99% of our application. things such as:
> easily hiding and showing columns
> easily dragging columns from one place to another
> easily extending the application if you add one more column to your
> list
> ability to fix the first few columns in a list so that they can’t be
> scrolled off window
> some ability to do entry into some columns
> you can display small icons and change colours on list lines to
> highlight important features
>
> we have all our headed lists composed from a table class so that we
> save the last look of the list for each user and restore that when
> they next log in. adding a new column to the list for is simply:
> add the field to the query class
> update the fields visibility in our data dictionary
> done — there are no further coding changes, or window changes at all
>
>
> I find that a headed list is pretty easy for our customers to grasp
> and they like the ability to move columns. it far outweighs complex
> grid — which we have to program everything for.
>
>
> when we converted from the classic world, we started off thinking
> everything was a complex grid, simply because thats what we were used
> to…
>
> until we discovered the sheer joy and simplicity of the headed list.
> its my favourite studio interface object.
>
>
>
>
>
>
> Doug Easterbrook
> Arts Management Systems Ltd.
> mailto:doug@artsman.com
> www.artsman.com
> Phone (403) 650-1978
>
>> On Aug 4, 2017, at 1:54 AM, Nick Renders <omnis1@arcict.com> wrote:
>>
>> Hi *
>>
>> I have a newbie question about the complex grid.
>>
>> Whenever I want to add an extra column in design mode,
>> I update the $columns property of the object. Omnis
>> adds a divider at the end, and I can start adding objects
>> in the new column.
>>
>> But how do I add a column in between 2 other columns?
>> Is there perhaps some way to re-order the columns in a
>> complex grid?
>>
>> The only way I have found is to drag fields from one
>> column to another, but that is really tedious work.
>> Am I missing something obvious?
>>
>> Best regards,
>>
>> Nick Renders
>>
>> _____________________________________________________________
>> Manage your list subscriptions at lists.omnis-dev.com

_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com