summaryrefslogtreecommitdiff
path: root/restrictions.md
diff options
context:
space:
mode:
authorPietro Gagliardi <[email protected]>2014-02-12 21:08:10 -0500
committerPietro Gagliardi <[email protected]>2014-02-12 21:08:10 -0500
commit3dcbb3920d2920f39a932251c757d21a3bf92cef (patch)
treeab29416ba847eaa733cba0a7dcd526ece63f80a9 /restrictions.md
parente296398eff57fb664918adb3caabbb46726530ce (diff)
Windows sysData has been adjusted to deal with child controls. Rather than storing the parent window, it is passed as an argument to sysData.make(), which does the child ID allocation. Child IDs are now window-local, getting rid of that restriction.
Diffstat (limited to 'restrictions.md')
-rw-r--r--restrictions.md1
1 files changed, 0 insertions, 1 deletions
diff --git a/restrictions.md b/restrictions.md
index 11466f8..72807c3 100644
--- a/restrictions.md
+++ b/restrictions.md
@@ -2,4 +2,3 @@ This is a file to keep track of API restrictions that simplify the implementatio
- Once you open a window, the controls are finalized: you cannot change the window's control or add/remove controls to layouts.
- Once you open a window, you cannot change its event channels or its controls's event channels.
-- [Windows] At most 65535 controls can be made, period. This is because child window IDs are alloted by the UI library application-global, not window-local, and BN_CLICKED only stores the control ID in a word (and I start counting at 1 to be safe). If I keep the first restriction and amend it such that you can only set the control of a window at the time of first open (somehow; split create and open?), I can easily make them window-local.