------------------------------
Toni Davenport
Uniface Community Edition Shared Account
US
------------------------------
------------------------------
Toni Davenport
Uniface Community Edition Shared Account
US
------------------------------
You'd have to then apply an operation to the panel button, and include that operation in all components with that panel.
Which version of Uniface?
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
You'd have to then apply an operation to the panel button, and include that operation in all components with that panel.
Which version of Uniface?
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
Hi all,
in older Uniface versions the same functionality of $putmess was obtained by this code snippet:
content = ""
call copyMsgFrame
sleep 2
content = $selblk
entry copyMsgFrame
macro "^MESSAGE^SELECT^TEXT^SAVE^ACCEPT "
end
(Note: in the macro string after the ACCEPT word a single space is available before the closing double quote.)
The macro used is still part of the current documentation as part of $selblk function samples.
Gianni
------------------------------
Gianni Sandigliano
IT
------------------------------
You'd have to then apply an operation to the panel button, and include that operation in all components with that panel.
Which version of Uniface?
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
I know in theory it would be safer to have my own form, just in case Uniface pulls standard functionality and of course if it got overwritten be a newer version, but just thought that as Uniface already handles much of it, it would be a simple thing to amend the uniface form and take the risk!?
------------------------------
Toni Davenport
Uniface Community Edition Shared Account
US
------------------------------
I know in theory it would be safer to have my own form, just in case Uniface pulls standard functionality and of course if it got overwritten be a newer version, but just thought that as Uniface already handles much of it, it would be a simple thing to amend the uniface form and take the risk!?
------------------------------
Toni Davenport
Uniface Community Edition Shared Account
US
------------------------------
Hi Toni,
Uniface puts its own stuff into message/frame in two cases:
- Uniface kernel errors
- $ioprint > 0
All contents inserted into MessageFrame from Uniface have their historical structure (which I really do NOT like!).
To recognize my own stuff I am usually defining them with a classical LOG structure:
[Timestamp] [User] [Node] [Process] [Level] [Case] [LongDescription (eventually structured)]
In this way contents could be filtered before being directed to someone/somewhere.
Hope it helps,
Gianni
------------------------------
Gianni Sandigliano
IT
------------------------------
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.