summaryrefslogtreecommitdiff
path: root/restrictions.md
diff options
context:
space:
mode:
authorPietro Gagliardi <[email protected]>2014-02-12 10:29:56 -0500
committerPietro Gagliardi <[email protected]>2014-02-12 10:29:56 -0500
commite9e2c0f269aac1157a3ea6a6021a86869fdd6888 (patch)
tree7edd6ae853fd47ea09972833bd74b3239674fcfa /restrictions.md
parent0f373195de316b1b20a05ebff1463fb8a56b1f1b (diff)
Set up restrictions tracking. Added a restriction that a window and its controls are fixed to the window once it has been open. Started accounting for parent windows in controls.
Diffstat (limited to 'restrictions.md')
-rw-r--r--restrictions.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/restrictions.md b/restrictions.md
new file mode 100644
index 0000000..11466f8
--- /dev/null
+++ b/restrictions.md
@@ -0,0 +1,5 @@
+This is a file to keep track of API restrictions that simplify the implementation of the package. I would like to eliminate them, but...
+
+- 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.