Posts: 878
Joined: 2007-08-14
Location: United States
The functions WinType and (WinList or WinName) are inconsistent in their parameters ...
// types returned by WinType
// 1: graphs 2: tables 3:layouts 5: notebooks 7: panels 13: XOPs
// types used by WinList and WinName
// 1: graphs 2: tables 4:layouts 16: notebooks 64: panels 128:procedures 4096:XOPs
I would like to have both WinType and WinList use consistent numbers and also have WinType return a valid number (non-zero) for a procedure window.
Recognizing that changes in WinType numbers will otherwise break many existing packages (ie, this is likely an IgorPro 7.0 feature request), at least having WinType return 128 for procedure windows would be immediately very helpful. Yes, I know the line about WinType ...
Since command and procedure windows do not have names (they only have titles),
WinType can not even be asked about those windows.
However, this rule is BROKEN by both WinList and WinName commands!
--
J. J. Weimer
Chemistry / Chemical & Materials Engineering, UAHuntsville
Posts: 289
Joined: 2007-07-19
Location: United States
jjweimer wrote:
The functions WinType and (WinList or WinName) are inconsistent in their parameters ...
However, this rule is BROKEN by both WinList and WinName commands!
To be precise, WinList and WinName have OVERCOME the restrictions of WinType :-)
Joined: 2007-08-14
Location: United States
The functions WinType and (WinList or WinName) are inconsistent in their parameters ...
// types returned by WinType
// 1: graphs 2: tables 3:layouts 5: notebooks 7: panels 13: XOPs
// types used by WinList and WinName
// 1: graphs 2: tables 4:layouts 16: notebooks 64: panels 128:procedures 4096:XOPs
I would like to have both WinType and WinList use consistent numbers and also have WinType return a valid number (non-zero) for a procedure window.
Recognizing that changes in WinType numbers will otherwise break many existing packages (ie, this is likely an IgorPro 7.0 feature request), at least having WinType return 128 for procedure windows would be immediately very helpful. Yes, I know the line about WinType ...
However, this rule is BROKEN by both WinList and WinName commands!
--
J. J. Weimer
Chemistry / Chemical & Materials Engineering, UAHuntsville