Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #10428 > unrolled thread

Numerous crashes, Firstly 5333. related to Graphs4VO and extra methods.

Started byMartin <Martin@spam.spam>
First post2017-04-13 14:01 +0100
Last post2017-05-05 14:24 +0200
Articles 6 — 3 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Numerous crashes, Firstly 5333. related to Graphs4VO and extra methods. Martin <Martin@spam.spam> - 2017-04-13 14:01 +0100
    Re: Numerous crashes, Firstly 5333. related to Graphs4VO and extra methods. Otto Christiaanse <ofchristiaanse@gmail.com> - 2017-04-18 01:49 -0700
      Re: Numerous crashes, Firstly 5333. related to Graphs4VO and extra methods. Martin <Martin@spam.spam> - 2017-04-25 12:02 +0100
        Re: Numerous crashes, Firstly 5333. related to Graphs4VO and extra methods. Otto Christiaanse <ofchristiaanse@gmail.com> - 2017-05-05 02:41 -0700
          Re: Numerous crashes, Firstly 5333. related to Graphs4VO and extra methods. Martin <Martin@spam.spam> - 2017-05-05 11:25 +0100
          Re: Numerous crashes, Firstly 5333. related to Graphs4VO and extra methods. "Wolfgang Riedmann" <wriedmann@gmail.com> - 2017-05-05 14:24 +0200

#10428 — Numerous crashes, Firstly 5333. related to Graphs4VO and extra methods.

FromMartin <Martin@spam.spam>
Date2017-04-13 14:01 +0100
SubjectNumerous crashes, Firstly 5333. related to Graphs4VO and extra methods.
Message-ID<ocnsl1$pqc$1@dont-email.me>
OK Some basic information

VO28 SP4
ADS 12 using ADS data dictionary

Windows Server 2012

Software is unreliable at this site.

Elsewhere is pretty reliable.

The people assigned to this task are old style computer staff who knew 
more about Netware and XP and previous. The main person has 30 years 
experience with Clipper!!!!

OK so I am not a new programmer, been using VO for over a decade, and 
learning all the time.

I have managed to make one small program reliable by installing it on 
the C drive, only goes about once a week. On other sites up for months 
at a time.

Industrial environment, hardware is OK, but not latest greatest, network 
is OK.

I will start with some 5333 errors, in my example, our main executable 
running on a mapped network drive on the server. The servers own drive 
shared.

Our tech support bod started up, opened up order entry (large datadialog 
with a few tabs), searched for an order (bbrowser), opened up document 
printing, (datadialog), and clicked on the required report radio button.

BANG error message
5333 RadioButton:Dispatch(11)

gencode 50 access violation

Hmm within the Graphics4VO library - this line of code 
VOSendMessage(SELF:owner:Handle(),WM_USER,225,LONG(_CAST,SELF:handle()))


Whole method below

METHOD dispatch(oE) CLASS RadioButton
// Dispatcher für diese Klasse.

// Das Event BM_SETCHECK wird generiert, wenn ein Radiobutton durch 
Klick oder durch
// Zuweisung geändert worden ist. Das Event wird an das owner-Window des 
Radiobuttons
// als WM_USER weitergegeben

// Da diese Message häufig ist, wird Sie an den Anfang des dispatchers 
gestellt.
IF oE:message ==  BM_SETCHECK
   IF SELF:owner:isvisible() .and. SELF:isvisible()
 
VOSendMessage(SELF:owner:Handle(),WM_USER,225,LONG(_CAST,SELF:handle()))
   ENDIF
ENDIF

// Returnwert an die Superklasse weitergeben.		
RETURN SUPER:dispatch(oE)


English translation of the comments

// Dispatcher for this class.

// The BM_SETCHECK event is generated when a radio button is clicked or 
pressed
// assignment has been changed. The event is sent to the owner window of 
the radio button
// as WM_USER

// Since this message is frequent, it is placed at the beginning of the 
dispatcher.

######################################
Basically what is this doing to cause a 5333 and why is it required?

I can remove it but would like to know why.
######################################

[toc] | [next] | [standalone]


#10466

FromOtto Christiaanse <ofchristiaanse@gmail.com>
Date2017-04-18 01:49 -0700
Message-ID<d296be6e-2c9f-4a0e-87e4-1d6115fb91a5@googlegroups.com>
In reply to#10428
On Thursday, April 13, 2017 at 3:01:16 PM UTC+2, Martin wrote:
> OK Some basic information
> 
> VO28 SP4
> ADS 12 using ADS data dictionary
> 
> Windows Server 2012
> 
> Software is unreliable at this site.
> 
> Elsewhere is pretty reliable.
> 
> The people assigned to this task are old style computer staff who knew 
> more about Netware and XP and previous. The main person has 30 years 
> experience with Clipper!!!!
> 
> OK so I am not a new programmer, been using VO for over a decade, and 
> learning all the time.
> 
> I have managed to make one small program reliable by installing it on 
> the C drive, only goes about once a week. On other sites up for months 
> at a time.
> 
> Industrial environment, hardware is OK, but not latest greatest, network 
> is OK.
> 
> I will start with some 5333 errors, in my example, our main executable 
> running on a mapped network drive on the server. The servers own drive 
> shared.
> 
> Our tech support bod started up, opened up order entry (large datadialog 
> with a few tabs), searched for an order (bbrowser), opened up document 
> printing, (datadialog), and clicked on the required report radio button.
> 
> BANG error message
> 5333 RadioButton:Dispatch(11)
> 
> gencode 50 access violation
> 
> Hmm within the Graphics4VO library - this line of code 
> VOSendMessage(SELF:owner:Handle(),WM_USER,225,LONG(_CAST,SELF:handle()))
> 
> 
> Whole method below
> 
> METHOD dispatch(oE) CLASS RadioButton
> // Dispatcher für diese Klasse.
> 
> // Das Event BM_SETCHECK wird generiert, wenn ein Radiobutton durch 
> Klick oder durch
> // Zuweisung geändert worden ist. Das Event wird an das owner-Window des 
> Radiobuttons
> // als WM_USER weitergegeben
> 
> // Da diese Message häufig ist, wird Sie an den Anfang des dispatchers 
> gestellt.
> IF oE:message ==  BM_SETCHECK
>    IF SELF:owner:isvisible() .and. SELF:isvisible()
>  
> VOSendMessage(SELF:owner:Handle(),WM_USER,225,LONG(_CAST,SELF:handle()))
>    ENDIF
> ENDIF
> 
> // Returnwert an die Superklasse weitergeben.		
> RETURN SUPER:dispatch(oE)
> 
> 
> English translation of the comments
> 
> // Dispatcher for this class.
> 
> // The BM_SETCHECK event is generated when a radio button is clicked or 
> pressed
> // assignment has been changed. The event is sent to the owner window of 
> the radio button
> // as WM_USER
> 
> // Since this message is frequent, it is placed at the beginning of the 
> dispatcher.
> 
> ######################################
> Basically what is this doing to cause a 5333 and why is it required?
> 
> I can remove it but would like to know why.
> ######################################

Are you using a webbrowser control by any chance?

[toc] | [prev] | [next] | [standalone]


#10488

FromMartin <Martin@spam.spam>
Date2017-04-25 12:02 +0100
Message-ID<odna5s$48b$1@dont-email.me>
In reply to#10466
No, just normal VO code.

I am trying to get rid of any annoyances like this as we get moaned at
Thanks

Martin

On 18/04/2017 09:49, Otto Christiaanse wrote:
> On Thursday, April 13, 2017 at 3:01:16 PM UTC+2, Martin wrote:
>> OK Some basic information
>>
>> VO28 SP4
>> ADS 12 using ADS data dictionary
>>
>> Windows Server 2012
>>
>> Software is unreliable at this site.
>>
>> Elsewhere is pretty reliable.
>>
>> The people assigned to this task are old style computer staff who knew
>> more about Netware and XP and previous. The main person has 30 years
>> experience with Clipper!!!!
>>
>> OK so I am not a new programmer, been using VO for over a decade, and
>> learning all the time.
>>
>> I have managed to make one small program reliable by installing it on
>> the C drive, only goes about once a week. On other sites up for months
>> at a time.
>>
>> Industrial environment, hardware is OK, but not latest greatest, network
>> is OK.
>>
>> I will start with some 5333 errors, in my example, our main executable
>> running on a mapped network drive on the server. The servers own drive
>> shared.
>>
>> Our tech support bod started up, opened up order entry (large datadialog
>> with a few tabs), searched for an order (bbrowser), opened up document
>> printing, (datadialog), and clicked on the required report radio button.
>>
>> BANG error message
>> 5333 RadioButton:Dispatch(11)
>>
>> gencode 50 access violation
>>
>> Hmm within the Graphics4VO library - this line of code
>> VOSendMessage(SELF:owner:Handle(),WM_USER,225,LONG(_CAST,SELF:handle()))
>>
>>
>> Whole method below
>>
>> METHOD dispatch(oE) CLASS RadioButton
>> // Dispatcher für diese Klasse.
>>
>> // Das Event BM_SETCHECK wird generiert, wenn ein Radiobutton durch
>> Klick oder durch
>> // Zuweisung geändert worden ist. Das Event wird an das owner-Window des
>> Radiobuttons
>> // als WM_USER weitergegeben
>>
>> // Da diese Message häufig ist, wird Sie an den Anfang des dispatchers
>> gestellt.
>> IF oE:message ==  BM_SETCHECK
>>    IF SELF:owner:isvisible() .and. SELF:isvisible()
>>
>> VOSendMessage(SELF:owner:Handle(),WM_USER,225,LONG(_CAST,SELF:handle()))
>>    ENDIF
>> ENDIF
>>
>> // Returnwert an die Superklasse weitergeben.		
>> RETURN SUPER:dispatch(oE)
>>
>>
>> English translation of the comments
>>
>> // Dispatcher for this class.
>>
>> // The BM_SETCHECK event is generated when a radio button is clicked or
>> pressed
>> // assignment has been changed. The event is sent to the owner window of
>> the radio button
>> // as WM_USER
>>
>> // Since this message is frequent, it is placed at the beginning of the
>> dispatcher.
>>
>> ######################################
>> Basically what is this doing to cause a 5333 and why is it required?
>>
>> I can remove it but would like to know why.
>> ######################################
>
> Are you using a webbrowser control by any chance?
>
No, just normal VO code.

I am trying to get rid of any annoyances like this as we get moaned at
Thanks

Martin

[toc] | [prev] | [next] | [standalone]


#10559

FromOtto Christiaanse <ofchristiaanse@gmail.com>
Date2017-05-05 02:41 -0700
Message-ID<dd36f69f-7a87-417e-ba82-29a3647048f4@googlegroups.com>
In reply to#10488
On Tuesday, April 25, 2017 at 1:02:21 PM UTC+2, Martin wrote:
> No, just normal VO code.
> 
> I am trying to get rid of any annoyances like this as we get moaned at
> Thanks
> 
> Martin
> 

Hate to bring it to you, but VO is end of life. Windows OS is moving forward, VO is standing still, and according to simpel relativity, using VO is making you move backward from perspective of the rest of the world.

Not an answer to your question, I know. I have similar issues: our frontend app is sometimes crashing (since a year or so) with no apparent reason...

With this kind of problems, don't try to be the hero, or you must know you can beat the dragon, other wise, just run with the rest of the world (.NET: XSharp e.g., you know my preference).

Regards,
Otto

[toc] | [prev] | [next] | [standalone]


#10562

FromMartin <Martin@spam.spam>
Date2017-05-05 11:25 +0100
Message-ID<oehjok$dt3$1@dont-email.me>
In reply to#10559
Actually I feel that often Windows is moving backwards not forwards.

Repos are around 250 MB

One full time programmer on VO, and one 3/4 full time.

Took us 5 years to go from Clipper to VO, and we are now comfortable 
with it.

Work is coming in thick and fast and too much to be able to rewrite yet 
again at the moment.

Everything is WIN32 and that should just work, if it doesn't due to 
Windows changes, Windows is at fault not VO.




On 05/05/2017 10:41, Otto Christiaanse wrote:
> On Tuesday, April 25, 2017 at 1:02:21 PM UTC+2, Martin wrote:
>> No, just normal VO code.
>>
>> I am trying to get rid of any annoyances like this as we get moaned at
>> Thanks
>>
>> Martin
>>
>
> Hate to bring it to you, but VO is end of life. Windows OS is moving forward, VO is standing still, and according to simpel relativity, using VO is making you move backward from perspective of the rest of the world.
>
> Not an answer to your question, I know. I have similar issues: our frontend app is sometimes crashing (since a year or so) with no apparent reason...
>
> With this kind of problems, don't try to be the hero, or you must know you can beat the dragon, other wise, just run with the rest of the world (.NET: XSharp e.g., you know my preference).
>
> Regards,
> Otto
>

[toc] | [prev] | [next] | [standalone]


#10564

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2017-05-05 14:24 +0200
Message-ID<en398jFc06aU1@mid.individual.net>
In reply to#10559
Hi Otto,

> Hate to bring it to you, but VO is end of life. Windows OS is moving
> forward, VO is standing still, and according to simpel relativity,
> using VO is making you move backward from perspective of the rest of
> the world.

I agree with you, and I hope that X# will be able to compile my VO
programs in a few weeks/months.

Of course, I will not be able to rewrite all my programs, so the GUI
classes (compiled with X#) will live several years from now on.

I'm waiting for the moment when VO as my main development platform is
replaced by XIDE...

Wolfgang


-- 

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web