Xailer & OZ Software

One request.
Is it possible to add a type beSKIP which will prevent "cursor" to rest
on a column ?
Or there is a way get this behaviour already ?
Regards,
David

David,
On what property?
In edit mode or always?
In read only mode check the event OnChange, while editing check the event
OnEdit.
Regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"david fung" <davfung@yahoo.com> escribió en el mensaje
news:45e05a4c$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
> One request.
>
> Is it possible to add a type beSKIP which will prevent "cursor" to rest on
> a column ?
>
> Or there is a way get this behaviour already ?
>
> Regards,
> David
>

David,
On what property?
In edit mode or always?
In read only mode check the event OnChange, while editing check the event
OnEdit.
Regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"david fung" <davfung@yahoo.com> escribió en el mensaje
news:45e05a4c$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
> One request.
>
> Is it possible to add a type beSKIP which will prevent "cursor" to rest on
> a column ?
>
> Or there is a way get this behaviour already ?
>
> Regards,
> David
>

for TBrwColumn Object type
"nEditType" property, it currently has beNONE, beGET, beGET_BUTTON,
beGET_LISTBOX, be_BUTTON, be_LISTBOX (6 types)
I just wonder a 7th type beSKIP be added so to prevent "cursor" to rest
on this column.
Regards,
David
Ignacio Ortiz de Zúñiga wrote:
> David,
>
> On what property?
> In edit mode or always?
>
> In read only mode check the event OnChange, while editing check the event
> OnEdit.
>
> Regards,
>

for TBrwColumn Object type
"nEditType" property, it currently has beNONE, beGET, beGET_BUTTON,
beGET_LISTBOX, be_BUTTON, be_LISTBOX (6 types)
I just wonder a 7th type beSKIP be added so to prevent "cursor" to rest
on this column.
Regards,
David
Ignacio Ortiz de Zúñiga wrote:
> David,
>
> On what property?
> In edit mode or always?
>
> In read only mode check the event OnChange, while editing check the event
> OnEdit.
>
> Regards,
>

the beSKIP that I suggested behave the same as beNONE except this column
will not be highlighted during both edit mode or not.
Regards,
David
david fung wrote:
> for TBrwColumn Object type
> "nEditType" property, it currently has beNONE, beGET, beGET_BUTTON,
> beGET_LISTBOX, be_BUTTON, be_LISTBOX (6 types)
>
> I just wonder a 7th type beSKIP be added so to prevent "cursor" to rest
> on this column.
>
> Regards,
> David
>
>
>
>
> Ignacio Ortiz de Zúñiga wrote:
>> David,
>>
>> On what property?
>> In edit mode or always?
>>
>> In read only mode check the event OnChange, while editing check the
>> event OnEdit.
>>
>> Regards,
>>

the beSKIP that I suggested behave the same as beNONE except this column
will not be highlighted during both edit mode or not.
Regards,
David
david fung wrote:
> for TBrwColumn Object type
> "nEditType" property, it currently has beNONE, beGET, beGET_BUTTON,
> beGET_LISTBOX, be_BUTTON, be_LISTBOX (6 types)
>
> I just wonder a 7th type beSKIP be added so to prevent "cursor" to rest
> on this column.
>
> Regards,
> David
>
>
>
>
> Ignacio Ortiz de Zúñiga wrote:
>> David,
>>
>> On what property?
>> In edit mode or always?
>>
>> In read only mode check the event OnChange, while editing check the
>> event OnEdit.
>>
>> Regards,
>>

David,
I suggest you trap de OnDrawCell event for that, in case you use a line
marquee style and the OnChange event to move to next or previous column. I
am afraid you proposal is not common, and it can provoke serious
incompatiblities issues with current implementation. Sorry.
Regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"david fung" <davfung@yahoo.com> escribió en el mensaje
news:[email=45e37fca@news.xailer.com...]45e37fca@news.xailer.com...[/email]
> the beSKIP that I suggested behave the same as beNONE except this column
> will not be highlighted during both edit mode or not.
>
> Regards,
> David
>
>
>
> david fung wrote:
>> for TBrwColumn Object type
>> "nEditType" property, it currently has beNONE, beGET, beGET_BUTTON,
>> beGET_LISTBOX, be_BUTTON, be_LISTBOX (6 types)
>>
>> I just wonder a 7th type beSKIP be added so to prevent "cursor" to rest
>> on this column.
>>
>> Regards,
>> David
>>
>>
>>
>>
>> Ignacio Ortiz de Zúñiga wrote:
>>> David,
>>>
>>> On what property?
>>> In edit mode or always?
>>>
>>> In read only mode check the event OnChange, while editing check the
>>> event OnEdit.
>>>
>>> Regards,
>>>

David,
I suggest you trap de OnDrawCell event for that, in case you use a line
marquee style and the OnChange event to move to next or previous column. I
am afraid you proposal is not common, and it can provoke serious
incompatiblities issues with current implementation. Sorry.
Regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"david fung" <davfung@yahoo.com> escribió en el mensaje
news:[email=45e37fca@news.xailer.com...]45e37fca@news.xailer.com...[/email]
> the beSKIP that I suggested behave the same as beNONE except this column
> will not be highlighted during both edit mode or not.
>
> Regards,
> David
>
>
>
> david fung wrote:
>> for TBrwColumn Object type
>> "nEditType" property, it currently has beNONE, beGET, beGET_BUTTON,
>> beGET_LISTBOX, be_BUTTON, be_LISTBOX (6 types)
>>
>> I just wonder a 7th type beSKIP be added so to prevent "cursor" to rest
>> on this column.
>>
>> Regards,
>> David
>>
>>
>>
>>
>> Ignacio Ortiz de Zúñiga wrote:
>>> David,
>>>
>>> On what property?
>>> In edit mode or always?
>>>
>>> In read only mode check the event OnChange, while editing check the
>>> event OnEdit.
>>>
>>> Regards,
>>>

Thank you for your reply.
I have no idea whether an implementation is feasible.
But like in an invoice entry program. In the invoice detail section,
after user had entered the item code, the next column should display the
description of the item. What I suggest is to have a way to skip this
description column so user can go on to the next column (say No. of
units purchased).
Attach is a capture from DBFData6 Sample application. The price column
is not editable, but the "cursor" do rest on this column (during non
:EDIT() mode), can it be skipped automatically like it does in :Edit() mode.
If not possible, it is OK. I just want to make the point clear, that's
all. Thanks
Regards,
David
Ignacio Ortiz de Zúñiga wrote:
> David,
>
> I suggest you trap de OnDrawCell event for that, in case you use a line
> marquee style and the OnChange event to move to next or previous column. I
> am afraid you proposal is not common, and it can provoke serious
> incompatiblities issues with current implementation. Sorry.
>
> Regards,
>
--

Thank you for your reply.
I have no idea whether an implementation is feasible.
But like in an invoice entry program. In the invoice detail section,
after user had entered the item code, the next column should display the
description of the item. What I suggest is to have a way to skip this
description column so user can go on to the next column (say No. of
units purchased).
Attach is a capture from DBFData6 Sample application. The price column
is not editable, but the "cursor" do rest on this column (during non
:EDIT() mode), can it be skipped automatically like it does in :Edit() mode.
If not possible, it is OK. I just want to make the point clear, that's
all. Thanks
Regards,
David
Ignacio Ortiz de Zúñiga wrote:
> David,
>
> I suggest you trap de OnDrawCell event for that, in case you use a line
> marquee style and the OnChange event to move to next or previous column. I
> am afraid you proposal is not common, and it can provoke serious
> incompatiblities issues with current implementation. Sorry.
>
> Regards,
>
--

David,
>>What I suggest is to have a way to skip this description column
oColumn:nEditType := beNONE
> Attach is a capture from DBFData6 Sample application. The price column
> is not editable, but the "cursor" do rest on this column (during non
> :EDIT() mode), can it be skipped automatically like it does in :Edit()
> mode.
I am afraid not straight forward, but it can be done trapping the OnChange
event and with a liitle work on your side.
Regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"david fung" <davfung@yahoo.com> escribió en el mensaje
news:[email=45e3f70f@news.xailer.com...]45e3f70f@news.xailer.com...[/email]
> Thank you for your reply.
>
> I have no idea whether an implementation is feasible.
>
>
> But like in an invoice entry program. In the invoice detail section,
> after user had entered the item code, the next column should display the
> description of the item. What I suggest is to have a way to skip this
> description column so user can go on to the next column (say No. of
> units purchased).
>
> Attach is a capture from DBFData6 Sample application. The price column
> is not editable, but the "cursor" do rest on this column (during non
> :EDIT() mode), can it be skipped automatically like it does in :Edit()
> mode.
>
> If not possible, it is OK. I just want to make the point clear, that's
> all. Thanks
>
> Regards,
> David
>
>
>
> Ignacio Ortiz de Zúñiga wrote:
>> David,
>>
>> I suggest you trap de OnDrawCell event for that, in case you use a line
>> marquee style and the OnChange event to move to next or previous column.
>> I
>> am afraid you proposal is not common, and it can provoke serious
>> incompatiblities issues with current implementation. Sorry.
>>
>> Regards,
>>
>
>

David,
>>What I suggest is to have a way to skip this description column
oColumn:nEditType := beNONE
> Attach is a capture from DBFData6 Sample application. The price column
> is not editable, but the "cursor" do rest on this column (during non
> :EDIT() mode), can it be skipped automatically like it does in :Edit()
> mode.
I am afraid not straight forward, but it can be done trapping the OnChange
event and with a liitle work on your side.
Regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"david fung" <davfung@yahoo.com> escribió en el mensaje
news:[email=45e3f70f@news.xailer.com...]45e3f70f@news.xailer.com...[/email]
> Thank you for your reply.
>
> I have no idea whether an implementation is feasible.
>
>
> But like in an invoice entry program. In the invoice detail section,
> after user had entered the item code, the next column should display the
> description of the item. What I suggest is to have a way to skip this
> description column so user can go on to the next column (say No. of
> units purchased).
>
> Attach is a capture from DBFData6 Sample application. The price column
> is not editable, but the "cursor" do rest on this column (during non
> :EDIT() mode), can it be skipped automatically like it does in :Edit()
> mode.
>
> If not possible, it is OK. I just want to make the point clear, that's
> all. Thanks
>
> Regards,
> David
>
>
>
> Ignacio Ortiz de Zúñiga wrote:
>> David,
>>
>> I suggest you trap de OnDrawCell event for that, in case you use a line
>> marquee style and the OnChange event to move to next or previous column.
>> I
>> am afraid you proposal is not common, and it can provoke serious
>> incompatiblities issues with current implementation. Sorry.
>>
>> Regards,
>>
>
>