Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #972 > unrolled thread
| Started by | "Jamal" <vodotnet_nospam@yahoo.com> |
|---|---|
| First post | 2011-04-30 11:42 -0400 |
| Last post | 2011-05-01 22:22 +0000 |
| Articles | 8 — 3 participants |
Back to article view | Back to comp.lang.clipper.visual-objects
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: bBrowser 2.0.8.0 RowSelect( ) "Jamal" <vodotnet_nospam@yahoo.com> - 2011-04-30 11:42 -0400
Re: bBrowser 2.0.8.0 RowSelect( ) "Stephen Quinn" <stevejqNO@bigpondSPAM.net.au> - 2011-05-01 10:15 +1000
Re: bBrowser 2.0.8.0 RowSelect( ) "Jamal" <vodotnet_nospam@yahoo.com> - 2011-04-30 23:56 -0400
Re: bBrowser 2.0.8.0 RowSelect( ) "Stephen Quinn" <stevejqNO@bigpondSPAM.net.au> - 2011-05-01 16:56 +1000
Re: bBrowser 2.0.8.0 RowSelect( ) "Geoff Schaller" <geoffx@softwarexobjectives.com.au> - 2011-05-01 22:22 +0000
Re: bBrowser 2.0.8.0 RowSelect( ) "Jamal" <vodotnet_nospam@yahoo.com> - 2011-05-01 19:54 -0400
Re: bBrowser 2.0.8.0 RowSelect( ) "Geoff Schaller" <geoffx@softwarexobjectives.com.au> - 2011-05-02 22:00 +0000
Re: bBrowser 2.0.8.0 RowSelect( ) "Geoff Schaller" <geoffx@softwarexobjectives.com.au> - 2011-05-01 22:22 +0000
| From | "Jamal" <vodotnet_nospam@yahoo.com> |
|---|---|
| Date | 2011-04-30 11:42 -0400 |
| Subject | Re: bBrowser 2.0.8.0 RowSelect( ) |
| Message-ID | <iphako$os5$1@dont-email.me> |
Geoff, I suspend notification already; commenting those extra calls did not break functionality. If you use bBrowser, add RowSelect() and see how many times it is called <g>. Jamal "Geoff Schaller" wrote in message news:4dbb53eb$0$77724$c30e37c6@exi-reader.telstra.net... Jamal. No - poor programming. You should re-enable the bBrowser functionality because it has other reasons for doing it that way. You are going to break other functionality. It is better to manage a 'state' flag to say your window is built and bBrowser has finished initialising. Now your "relation" mechanism can be enabled off that method. Another way to achieve the same thing is to turn off notification so that RowSelect does not fire. But the KID stack error is yours - you are not managing objects properly or you have regressive loops of some kind. Geoff "Jamal" <vodotnet_nospam@yahoo.com> wrote in message news:ipfg5q$p4l$1@dont-email.me: > I am using bBrowser 2.0.8.0 under VO 2837 and I faced a KID size limit > exceeded messages. > > I traced the issue to RowSelect( ) callback method being called so many > times during the Use(), Notify( ) and various other methods. In fact, the > RowSelect( ) was called Number Of Records listed in the bBrowser upon > initial load! Imagine if you have thousands of records being loaded! > > I used the RowSelect( ) to load related child data into another bBrowser > window based on the row selected in the the first bBrowser window. In the > second bBrowser clear scope and set scope based on data selected in first > bBrowser. > > I initially thought based on the vague documentation that it is invoked > when > the user either clicks or selects the row via keyboard, but due to due to > internal calls in various bBrowser methods, which I think are unnecessary > calls, caused the KID stack to reach its limit. > > From the docs: "bBrowser:RowSelect() is a callback method that is called > by > the bBrowser whenever another row is selected." > > Since I have source code, I commented out all those unnecessary calls ( > except in NotifyRecordChange( ) ), and loading the bBrowser is now faster > and without the KID stack errors. > The same goes for CellSelect( ) but I have no use for it at this time. > > Just thought to share this info. Are those issues resolved in 3.0 or 4.0? > > Jamal
[toc] | [next] | [standalone]
| From | "Stephen Quinn" <stevejqNO@bigpondSPAM.net.au> |
|---|---|
| Date | 2011-05-01 10:15 +1000 |
| Message-ID | <jB1vp.3072$CS3.221@viwinnwfe01.internal.bigpond.com> |
| In reply to | #972 |
Jamal
> I suspend notification already; commenting those extra calls did not break
> functionality.
Where & when in the code
- you may be to late in the sequence when you call SuspendNotifcation()
> If you use bBrowser, add RowSelect() and see how many times it is called
It's already in bBrowser - here is no need to add it.
If your using your own RowSelect() callback then show us the code
- that's more than likely where the problem is.
>> I used the RowSelect( ) to load related child data into another bBrowser
>> window based on the row selected in the the first bBrowser window. In the
>> second bBrowser clear scope and set scope based on data selected in first
>> bBrowser.
Just noticed this in your original query
- why aren't you using a SetSelectiveRelation() to fill the child
bBrowser??
- RowSelect() IMO is not the way to go for this type of functionality
CYA
Steve
[toc] | [prev] | [next] | [standalone]
| From | "Jamal" <vodotnet_nospam@yahoo.com> |
|---|---|
| Date | 2011-04-30 23:56 -0400 |
| Message-ID | <ipill8$ake$1@dont-email.me> |
| In reply to | #1003 |
Stephen,
I wanted RowSelect( ) to act a row click and I achieve it by doing code
profiling to minimize the number of calls and see what was slowing down the
bBrowser.
I used SetSelectiveRelation() before but it hand some side effects which I
am not going to discuss here, that I went the RowSelect( ) route.
Anyway, the post was to bring attention to the issue I raised initially just
in case someone else runs into the same situation.
Jamal
"Stephen Quinn" wrote in message
news:jB1vp.3072$CS3.221@viwinnwfe01.internal.bigpond.com...
Jamal
> I suspend notification already; commenting those extra calls did not break
> functionality.
Where & when in the code
- you may be to late in the sequence when you call SuspendNotifcation()
> If you use bBrowser, add RowSelect() and see how many times it is called
It's already in bBrowser - here is no need to add it.
If your using your own RowSelect() callback then show us the code
- that's more than likely where the problem is.
>> I used the RowSelect( ) to load related child data into another bBrowser
>> window based on the row selected in the the first bBrowser window. In the
>> second bBrowser clear scope and set scope based on data selected in first
>> bBrowser.
Just noticed this in your original query
- why aren't you using a SetSelectiveRelation() to fill the child
bBrowser??
- RowSelect() IMO is not the way to go for this type of functionality
CYA
Steve
[toc] | [prev] | [next] | [standalone]
| From | "Stephen Quinn" <stevejqNO@bigpondSPAM.net.au> |
|---|---|
| Date | 2011-05-01 16:56 +1000 |
| Message-ID | <yt7vp.3069$aH5.792@viwinnwfe02.internal.bigpond.com> |
| In reply to | #1004 |
Jamal
> I wanted RowSelect( ) to act a row click and I achieve it by doing code
You achieve the same result when you use the Notify() method of the window
eg when not using a SetSelectiveRelation()
CASE nNotify = NOTIFY_RECORDCHANGE
// Check to see which control caused the message
IF oEvent:Control: NameSym = #PARENT
// Update child details using a scoped index
uTop := SELF;oParentServer:fieldget(#AFIELD)
SELF:oChildServer:SetScope(uTop)
ENDIF
If you don't have a SetScope() in your DBServer code yet, something along
the lines of
METHOD SetScope( xTop, xBottom ) CLASS MyDBServer
Default( @xBottom, xTop)
SELF:SuspendNotification()
SELF:SetScopeTop( xTop )
SELF:SetScopeBottom(xBottom)
SELF:ResetNotification()
SELF:GoTop()
RETURN
Check the method/function names & syntax though<bg>
And I didn't change anything in the bBrowser source code to achieve it<bg>
As you can see I program the DBServers not the bBrowsers
CYA
Steve
[toc] | [prev] | [next] | [standalone]
| From | "Geoff Schaller" <geoffx@softwarexobjectives.com.au> |
|---|---|
| Date | 2011-05-01 22:22 +0000 |
| Message-ID | <4dbddd0e$0$99951$c30e37c6@exi-reader.telstra.net> |
| In reply to | #1004 |
Jamal, The purpose of your post was only that it showed us all you have a coding mistake, so you aren't helping anyone else at all. Now, we can help you find your mistake if you like but you will have to show us some code. Finding the source of your problem may then be of assistance to others. Geoff "Jamal" <vodotnet_nospam@yahoo.com> wrote in message news:ipill8$ake$1@dont-email.me: > Stephen, > > I wanted RowSelect( ) to act a row click and I achieve it by doing code > profiling to minimize the number of calls and see what was slowing down the > bBrowser. > I used SetSelectiveRelation() before but it hand some side effects which I > am not going to discuss here, that I went the RowSelect( ) route. > Anyway, the post was to bring attention to the issue I raised initially just > in case someone else runs into the same situation. > > Jamal > > > "Stephen Quinn" wrote in message > news:jB1vp.3072$CS3.221@viwinnwfe01.internal.bigpond.com... > > Jamal > > > > I suspend notification already; commenting those extra calls did not break > > functionality. > > Where & when in the code > - you may be to late in the sequence when you call SuspendNotifcation() > > > > If you use bBrowser, add RowSelect() and see how many times it is called > > It's already in bBrowser - here is no need to add it. > > If your using your own RowSelect() callback then show us the code > - that's more than likely where the problem is. > > > >> I used the RowSelect( ) to load related child data into another bBrowser > >> window based on the row selected in the the first bBrowser window. In the > >> second bBrowser clear scope and set scope based on data selected in first > >> bBrowser. > > Just noticed this in your original query > - why aren't you using a SetSelectiveRelation() to fill the child > bBrowser?? > - RowSelect() IMO is not the way to go for this type of functionality > > CYA > Steve
[toc] | [prev] | [next] | [standalone]
| From | "Jamal" <vodotnet_nospam@yahoo.com> |
|---|---|
| Date | 2011-05-01 19:54 -0400 |
| Message-ID | <ipkrs8$9uj$1@dont-email.me> |
| In reply to | #1011 |
Geoff, I was not looking for help, just sharing an observation that RowSelect( ) is being too many times which in some may lead some side effects. SuspendNotification( ) definitely helps with KID limits. Jamal "Geoff Schaller" wrote in message news:4dbddd0e$0$99951$c30e37c6@exi-reader.telstra.net... Jamal, The purpose of your post was only that it showed us all you have a coding mistake, so you aren't helping anyone else at all. Now, we can help you find your mistake if you like but you will have to show us some code. Finding the source of your problem may then be of assistance to others. Geoff "Jamal" <vodotnet_nospam@yahoo.com> wrote in message news:ipill8$ake$1@dont-email.me: > Stephen, > > I wanted RowSelect( ) to act a row click and I achieve it by doing code > profiling to minimize the number of calls and see what was slowing down > the > bBrowser. > I used SetSelectiveRelation() before but it hand some side effects which I > am not going to discuss here, that I went the RowSelect( ) route. > Anyway, the post was to bring attention to the issue I raised initially > just > in case someone else runs into the same situation. > > Jamal > > > "Stephen Quinn" wrote in message > news:jB1vp.3072$CS3.221@viwinnwfe01.internal.bigpond.com... > > Jamal > > > > I suspend notification already; commenting those extra calls did not > > break > > functionality. > > Where & when in the code > - you may be to late in the sequence when you call > SuspendNotifcation() > > > > If you use bBrowser, add RowSelect() and see how many times it is called > > It's already in bBrowser - here is no need to add it. > > If your using your own RowSelect() callback then show us the code > - that's more than likely where the problem is. > > > >> I used the RowSelect( ) to load related child data into another > >> bBrowser > >> window based on the row selected in the the first bBrowser window. In > >> the > >> second bBrowser clear scope and set scope based on data selected in > >> first > >> bBrowser. > > Just noticed this in your original query > - why aren't you using a SetSelectiveRelation() to fill the child > bBrowser?? > - RowSelect() IMO is not the way to go for this type of functionality > > CYA > Steve
[toc] | [prev] | [next] | [standalone]
| From | "Geoff Schaller" <geoffx@softwarexobjectives.com.au> |
|---|---|
| Date | 2011-05-02 22:00 +0000 |
| Message-ID | <4dbf2961$0$99964$c30e37c6@exi-reader.telstra.net> |
| In reply to | #1014 |
But you used it incorrectly. "Jamal" <vodotnet_nospam@yahoo.com> wrote in message news:ipkrs8$9uj$1@dont-email.me: > Geoff, > > I was not looking for help, just sharing an observation that RowSelect( ) is > being too many times which in some may lead some side effects. > SuspendNotification( ) definitely helps with KID limits. > > Jamal > > > > "Geoff Schaller" wrote in message > news:4dbddd0e$0$99951$c30e37c6@exi-reader.telstra.net... > > Jamal, > > The purpose of your post was only that it showed us all you have a > coding mistake, so you aren't helping anyone else at all. Now, we can > help you find your mistake if you like but you will have to show us some > code. Finding the source of your problem may then be of assistance to > others. > > Geoff > > > > "Jamal" <vodotnet_nospam@yahoo.com> wrote in message > news:ipill8$ake$1@dont-email.me: > > > > Stephen, > > > > I wanted RowSelect( ) to act a row click and I achieve it by doing code > > profiling to minimize the number of calls and see what was slowing down > > the > > bBrowser. > > I used SetSelectiveRelation() before but it hand some side effects which I > > am not going to discuss here, that I went the RowSelect( ) route. > > Anyway, the post was to bring attention to the issue I raised initially > > just > > in case someone else runs into the same situation. > > > > Jamal > > > > > > "Stephen Quinn" wrote in message > > news:jB1vp.3072$CS3.221@viwinnwfe01.internal.bigpond.com... > > > > Jamal > > > > > > > > I suspend notification already; commenting those extra calls did not > > > break > > > functionality. > > > > > Where & when in the code > > - you may be to late in the sequence when you call > > SuspendNotifcation() > > > > > > > > If you use bBrowser, add RowSelect() and see how many times it is called > > > > > It's already in bBrowser - here is no need to add it. > > > > If your using your own RowSelect() callback then show us the code > > - that's more than likely where the problem is. > > > > > > > >> I used the RowSelect( ) to load related child data into another > > >> bBrowser > > >> window based on the row selected in the the first bBrowser window. In > > >> the > > >> second bBrowser clear scope and set scope based on data selected in > > >> first > > >> bBrowser. > > > > > Just noticed this in your original query > > - why aren't you using a SetSelectiveRelation() to fill the child > > bBrowser?? > > - RowSelect() IMO is not the way to go for this type of functionality > > > > CYA > > Steve
[toc] | [prev] | [next] | [standalone]
| From | "Geoff Schaller" <geoffx@softwarexobjectives.com.au> |
|---|---|
| Date | 2011-05-01 22:22 +0000 |
| Message-ID | <4dbddd0d$0$99950$c30e37c6@exi-reader.telstra.net> |
| In reply to | #972 |
You haven't shown us the code so it is very difficult to assist. You are obviously doing something wrong. Geoff "Jamal" <vodotnet_nospam@yahoo.com> wrote in message news:iphako$os5$1@dont-email.me: > Geoff, > > I suspend notification already; commenting those extra calls did not break > functionality. > If you use bBrowser, add RowSelect() and see how many times it is called > <g>. > > Jamal > > "Geoff Schaller" wrote in message > news:4dbb53eb$0$77724$c30e37c6@exi-reader.telstra.net... > > Jamal. > > No - poor programming. You should re-enable the bBrowser functionality > because it has other reasons for doing it that way. You are going to > break other functionality. > > It is better to manage a 'state' flag to say your window is built and > bBrowser has finished initialising. Now your "relation" mechanism can be > enabled off that method. Another way to achieve the same thing is to > turn off notification so that RowSelect does not fire. > > But the KID stack error is yours - you are not managing objects properly > or you have regressive loops of some kind. > > Geoff > > > > "Jamal" <vodotnet_nospam@yahoo.com> wrote in message > news:ipfg5q$p4l$1@dont-email.me: > > > > I am using bBrowser 2.0.8.0 under VO 2837 and I faced a KID size limit > > exceeded messages. > > > > I traced the issue to RowSelect( ) callback method being called so many > > times during the Use(), Notify( ) and various other methods. In fact, the > > RowSelect( ) was called Number Of Records listed in the bBrowser upon > > initial load! Imagine if you have thousands of records being loaded! > > > > I used the RowSelect( ) to load related child data into another bBrowser > > window based on the row selected in the the first bBrowser window. In the > > second bBrowser clear scope and set scope based on data selected in first > > bBrowser. > > > > I initially thought based on the vague documentation that it is invoked > > when > > the user either clicks or selects the row via keyboard, but due to due to > > internal calls in various bBrowser methods, which I think are unnecessary > > calls, caused the KID stack to reach its limit. > > > > From the docs: "bBrowser:RowSelect() is a callback method that is called > > by > > the bBrowser whenever another row is selected." > > > > Since I have source code, I commented out all those unnecessary calls ( > > except in NotifyRecordChange( ) ), and loading the bBrowser is now faster > > and without the KID stack errors. > > The same goes for CellSelect( ) but I have no use for it at this time. > > > > Just thought to share this info. Are those issues resolved in 3.0 or 4.0? > > > > Jamal
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.clipper.visual-objects
csiph-web