[WD55] Procedures non visible dans l'editeur d'etats
5 réponses
Peter
Bonjour,
Je sais que dans l'editeur d'etat (report editor) c'est possible de
editer/voir les procedures internes de l'etat comme _init(),
_imprimer_block_zzzz() etc.
Le probleme: je ne sais plus comment (ctrl/shift/123 dans le code-editor
ou quelque chose ... )
Cette action est irreversible, confirmez la suppression du commentaire ?
Signaler le commentaire
Veuillez sélectionner un problème
Nudité
Violence
Harcèlement
Fraude
Vente illégale
Discours haineux
Terrorisme
Autre
Peter
Bonjour,
Je sais que dans l'editeur d'etat (report editor) c'est possible de editer/voir les procedures internes de l'etat comme _init(), _imprimer_block_zzzz() etc.
Le probleme: je ne sais plus comment (ctrl/shift/123 dans le code-editor ou quelque chose ... )
Open WDEtat, go to the menu '?' > 'About WDEtat ...'. Press [ALT]-d check 'Generated procedures are visible', save the report, exit, open the report again, 'F8', et voila, the iSubstBloc(), iTerminePage() codes & much more, are there. (Thanks to Theo van Vliet)
-- Peter
Bonjour,
Je sais que dans l'editeur d'etat (report editor) c'est possible de
editer/voir les procedures internes de l'etat comme _init(),
_imprimer_block_zzzz() etc.
Le probleme: je ne sais plus comment (ctrl/shift/123 dans le code-editor
ou quelque chose ... )
Open WDEtat, go to the menu '?' > 'About WDEtat ...'. Press [ALT]-d
check 'Generated procedures are visible', save the report, exit, open
the report again, 'F8', et voila, the iSubstBloc(), iTerminePage()
codes & much more, are there.
(Thanks to Theo van Vliet)
Je sais que dans l'editeur d'etat (report editor) c'est possible de editer/voir les procedures internes de l'etat comme _init(), _imprimer_block_zzzz() etc.
Le probleme: je ne sais plus comment (ctrl/shift/123 dans le code-editor ou quelque chose ... )
Open WDEtat, go to the menu '?' > 'About WDEtat ...'. Press [ALT]-d check 'Generated procedures are visible', save the report, exit, open the report again, 'F8', et voila, the iSubstBloc(), iTerminePage() codes & much more, are there. (Thanks to Theo van Vliet)
-- Peter
Pascal H
Peter a écrit dans news:400d345d$0$333$:
Bonjour,
Je sais que dans l'editeur d'etat (report editor) c'est possible de editer/voir les procedures internes de l'etat comme _init(), _imprimer_block_zzzz() etc.
Le probleme: je ne sais plus comment (ctrl/shift/123 dans le code-editor ou quelque chose ... )
Open WDEtat, go to the menu '?' > 'About WDEtat ...'. Press [ALT]-d check 'Generated procedures are visible', save the report, exit, open the report again, 'F8', et voila, the iSubstBloc(), iTerminePage() codes & much more, are there. (Thanks to Theo van Vliet)
Great and useful ! Thanks for the tip, Peter (and Theo !). I'll put it in the T&T on then Windasso website.
And if I understand well, the hidden events that are shown with this combo may be modified and updated with self-made code ?
-- Pascal
Peter <petervu_morethan100spamsadayistomuch_@xs4all.nl> a écrit dans
news:400d345d$0$333$e4fe514c@news.xs4all.nl:
Bonjour,
Je sais que dans l'editeur d'etat (report editor) c'est possible
de editer/voir les procedures internes de l'etat comme _init(),
_imprimer_block_zzzz() etc.
Le probleme: je ne sais plus comment (ctrl/shift/123 dans le
code-editor ou quelque chose ... )
Open WDEtat, go to the menu '?' > 'About WDEtat ...'. Press
[ALT]-d check 'Generated procedures are visible', save the
report, exit, open the report again, 'F8', et voila, the
iSubstBloc(), iTerminePage() codes & much more, are there.
(Thanks to Theo van Vliet)
Great and useful !
Thanks for the tip, Peter (and Theo !).
I'll put it in the T&T on then Windasso website.
And if I understand well, the hidden events that are shown with this
combo may be modified and updated with self-made code ?
Je sais que dans l'editeur d'etat (report editor) c'est possible de editer/voir les procedures internes de l'etat comme _init(), _imprimer_block_zzzz() etc.
Le probleme: je ne sais plus comment (ctrl/shift/123 dans le code-editor ou quelque chose ... )
Open WDEtat, go to the menu '?' > 'About WDEtat ...'. Press [ALT]-d check 'Generated procedures are visible', save the report, exit, open the report again, 'F8', et voila, the iSubstBloc(), iTerminePage() codes & much more, are there. (Thanks to Theo van Vliet)
Great and useful ! Thanks for the tip, Peter (and Theo !). I'll put it in the T&T on then Windasso website.
And if I understand well, the hidden events that are shown with this combo may be modified and updated with self-made code ?
-- Pascal
Frederic Seret
Essaie avec F2
Pascal H wrote:
Peter a écrit dans news:400d345d$0$333$:
Bonjour,
Je sais que dans l'editeur d'etat (report editor) c'est possible de editer/voir les procedures internes de l'etat comme _init(), _imprimer_block_zzzz() etc.
Le probleme: je ne sais plus comment (ctrl/shift/123 dans le code-editor ou quelque chose ... )
Open WDEtat, go to the menu '?' > 'About WDEtat ...'. Press [ALT]-d check 'Generated procedures are visible', save the report, exit, open the report again, 'F8', et voila, the iSubstBloc(), iTerminePage() codes & much more, are there. (Thanks to Theo van Vliet)
Great and useful ! Thanks for the tip, Peter (and Theo !). I'll put it in the T&T on then Windasso website.
And if I understand well, the hidden events that are shown with this combo may be modified and updated with self-made code ?
Essaie avec F2
Pascal H wrote:
Peter <petervu_morethan100spamsadayistomuch_@xs4all.nl> a écrit dans
news:400d345d$0$333$e4fe514c@news.xs4all.nl:
Bonjour,
Je sais que dans l'editeur d'etat (report editor) c'est possible
de editer/voir les procedures internes de l'etat comme _init(),
_imprimer_block_zzzz() etc.
Le probleme: je ne sais plus comment (ctrl/shift/123 dans le
code-editor ou quelque chose ... )
Open WDEtat, go to the menu '?' > 'About WDEtat ...'. Press
[ALT]-d check 'Generated procedures are visible', save the
report, exit, open the report again, 'F8', et voila, the
iSubstBloc(), iTerminePage() codes & much more, are there.
(Thanks to Theo van Vliet)
Great and useful !
Thanks for the tip, Peter (and Theo !).
I'll put it in the T&T on then Windasso website.
And if I understand well, the hidden events that are shown with this
combo may be modified and updated with self-made code ?
Je sais que dans l'editeur d'etat (report editor) c'est possible de editer/voir les procedures internes de l'etat comme _init(), _imprimer_block_zzzz() etc.
Le probleme: je ne sais plus comment (ctrl/shift/123 dans le code-editor ou quelque chose ... )
Open WDEtat, go to the menu '?' > 'About WDEtat ...'. Press [ALT]-d check 'Generated procedures are visible', save the report, exit, open the report again, 'F8', et voila, the iSubstBloc(), iTerminePage() codes & much more, are there. (Thanks to Theo van Vliet)
Great and useful ! Thanks for the tip, Peter (and Theo !). I'll put it in the T&T on then Windasso website.
And if I understand well, the hidden events that are shown with this combo may be modified and updated with self-made code ?
Peter
Pascal H wrote:
[cut]
And if I understand well, the hidden events that are shown with this combo may be modified and updated with self-made code ?
Yes, but be careful. I think (not sure) that with a recompile the default procedures are back, the WDE is bigger and WDEtat, already not that stable in WD55, is even quicker with GPF'ing.
Can be practical when necessary, but used only 2 times in about 3 years.
Regards,
-- Peter
Pascal H wrote:
[cut]
And if I understand well, the hidden events that are shown with this
combo may be modified and updated with self-made code ?
Yes, but be careful.
I think (not sure) that with a recompile the default procedures are
back, the WDE is bigger and WDEtat, already not that stable in WD55,
is even quicker with GPF'ing.
Can be practical when necessary, but used only 2 times in about 3 years.
And if I understand well, the hidden events that are shown with this combo may be modified and updated with self-made code ?
Yes, but be careful. I think (not sure) that with a recompile the default procedures are back, the WDE is bigger and WDEtat, already not that stable in WD55, is even quicker with GPF'ing.
Can be practical when necessary, but used only 2 times in about 3 years.
Regards,
-- Peter
Pascal H
Peter a écrit dans news:400fd2a3$0$330$:
Pascal H wrote:
[cut]
And if I understand well, the hidden events that are shown with this combo may be modified and updated with self-made code ?
Yes, but be careful. I think (not sure) that with a recompile the default procedures are back, the WDE is bigger and WDEtat, already not that stable in WD55, is even quicker with GPF'ing.
Can be practical when necessary, but used only 2 times in about 3 years.
Regards,
I tried to add my own code in the 'revealated' part of the source and my report stayed frozen during the execution in test mode. As I noticed that there are some strange control characters at the end of the lines which should certainly not be removed, this maybe means that the code is precompiled.
In conclusion, I think this tip has to be used only if you want to trace all the code during execution.
---
J'ai essayé d'ajouter mon propre code dans la partie 'révélée' du source et mon état est resté gelé durant l'exécution en mode test. Comme j'ai remarqué qu'il y avait des caractères de contrôle bizarre à la fin des lignes qui ne devraient certainement pas être enlevés, ceci signifie probablement que le code est précompilé. En conclusion, je pense que cette astuce ne doit être utilisée que lorsque l'on souhaite tracer tout le code pendant l'exécution.
-- Pascal
Peter <petervu_morethan100spamsadayistomuch_@xs4all.nl> a écrit dans
news:400fd2a3$0$330$e4fe514c@news.xs4all.nl:
Pascal H wrote:
[cut]
And if I understand well, the hidden events that are shown with
this combo may be modified and updated with self-made code ?
Yes, but be careful.
I think (not sure) that with a recompile the default procedures
are back, the WDE is bigger and WDEtat, already not that stable in
WD55, is even quicker with GPF'ing.
Can be practical when necessary, but used only 2 times in about 3
years.
Regards,
I tried to add my own code in the 'revealated' part of the source and
my report stayed frozen during the execution in test mode.
As I noticed that there are some strange control characters at the end
of the lines which should certainly not be removed, this maybe means
that the code is precompiled.
In conclusion, I think this tip has to be used only if you want to
trace all the code during execution.
---
J'ai essayé d'ajouter mon propre code dans la partie 'révélée' du
source et mon état est resté gelé durant l'exécution en mode test.
Comme j'ai remarqué qu'il y avait des caractères de contrôle bizarre à
la fin des lignes qui ne devraient certainement pas être enlevés, ceci
signifie probablement que le code est précompilé.
En conclusion, je pense que cette astuce ne doit être utilisée que
lorsque l'on souhaite tracer tout le code pendant l'exécution.
And if I understand well, the hidden events that are shown with this combo may be modified and updated with self-made code ?
Yes, but be careful. I think (not sure) that with a recompile the default procedures are back, the WDE is bigger and WDEtat, already not that stable in WD55, is even quicker with GPF'ing.
Can be practical when necessary, but used only 2 times in about 3 years.
Regards,
I tried to add my own code in the 'revealated' part of the source and my report stayed frozen during the execution in test mode. As I noticed that there are some strange control characters at the end of the lines which should certainly not be removed, this maybe means that the code is precompiled.
In conclusion, I think this tip has to be used only if you want to trace all the code during execution.
---
J'ai essayé d'ajouter mon propre code dans la partie 'révélée' du source et mon état est resté gelé durant l'exécution en mode test. Comme j'ai remarqué qu'il y avait des caractères de contrôle bizarre à la fin des lignes qui ne devraient certainement pas être enlevés, ceci signifie probablement que le code est précompilé. En conclusion, je pense que cette astuce ne doit être utilisée que lorsque l'on souhaite tracer tout le code pendant l'exécution.
