Zitat:

---

Total, Visible und Top != Max, Min, Value.

Die Logik die dahintersteckt ist eine ganz andere.

Und um nochmal zur Frage zurückzukehren, woher das Bedürfnis die interne Repräsentation auf 0..0xFFFF zu normalisieren?

---

assembler code:

---

IDCMP_EXTENDEDMOUSE	=	$08000000
IMSGCODE_INTUIWHEELDATA	=	1<<15

 STRUCTURE	IntuiWheelData,0
	UWORD	iwd_Version	; version of this structure (see below)
	UWORD	iwd_Reserved	; always 0, reserved for future use
	WORD	iwd_WheelX	; horizontal wheel movement delta
	WORD	iwd_WheelY	; vertical wheel movement delta

INTUIWHEELDATA_VERSION	=	1

---

assmebler code:

---

check_wheel	cmp.l	#IDCMP_EXTENDEDMOUSE,im_Class(a1)
		bne	.rts

		cmp.w	#IMSGCODE_INTUIWHEELDATA,im_Code(a1)
		bne	.rts

		move.l	im_IAddress(a1),a0
		cmp.w	#INTUIWHEELDATA_VERSION,iwd_Version(a0)
		bne	.rts

		tst.w	iwd_WheelY(a0)
		blt	.wheelup
		bgt	.wheeldown
.rts		rts

---

asm code:

---

.test_wheel	cmp.w	#$7a,im_Code(a1)	; mouse wheel up
		beq	.wheelup

		cmp.w	#$7b,im_Code(a1)	; mouse wheel down
		beq	.wheeldown

---

.i code:

---

STRUCTURE	oxObject,0
	STRUCT	oxO_node,MLN_SIZE
	STRUCT	oxO_list,MLH_SIZE
	APTR	oxO_parent
	APTR	oxO_binding
	STRUCT	oxO_notifys,MLH_SIZE
	APTR	oxO_class
	UBYTE	oxO_flags
	UBYTE	oxO_hotkey
	APTR	oxO_prev		; for connection when pressing tabulator to focus next or prev object
	APTR	oxO_next		; ..
	APTR	oxO_drawinfo
	APTR	oxO_userbase		; the create() function takes a parameter in a1 that is a pointer to
					; a custom space where f.e. the app has its globals and it is needed
					; to have a pointer to them in the hook functions of the objects ...
					; but the main purpose of this field is that XUI stores pointers here
					; via the OX_PUTPTR and OX_RELPTR tag-commands

	APTR	oxO_userdata		; custom pointer or value set to what ever by the app
	ULONG	oxO_id			; custom field intended for search

	UWORD	oxO_left
	UWORD	oxO_top
	UWORD	oxO_width
	UWORD	oxO_height

	LABEL	oxO_SIZEOF

	BITDEF	oxO,INITIALIZED,0
	BITDEF	oxO,VISIBLE,1
	BITDEF	oxO,GHOSTED,2		; clickable?
	BITDEF	oxO,SLEEPING,3		; get no intuimessages like in ghost mode but stay fully visible,
					; sleeping widgets are skipped in the tabulator chain
	BITDEF	oxO,ACTIVE,4
	BITDEF	oxO,REFRESH,5		; refresh this gadget in next refresh run ..all childs of this gadget
					; are also refreshed

---

code:

---

ENUM	OX_METHODS

	EITEM	OXM_SET	; a1 oxm_set
	EITEM	OXM_GET	; a1 oxm_get

	EITEM	OXM_ADD	; a0 dest, a1 member		allow custom add-function for class
			;				example: window adds members to inner frame

	; ox objects are created and freed from central,
	; dispatchers do private work on them

	EITEM	OXM_SETDEF	; do this before tags are read to set default values

	EITEM	OXM_INIT
	EITEM	OXM_DEINIT
	EITEM	OXM_ACTIVATE
	EITEM	OXM_INACTIVE

	EITEM	OXM_INTUIMESSAGE

	EITEM	OXM_GETLAYOUT	; a1 oxLayoutInfo
	EITEM	OXM_SETLAYOUT	; ..  ..
	EITEM	OXM_setprop
	EITEM	OXM_DRAW	; draw (no sizes calculations)
	EITEM	OXM_DROPGFXBUFFERS
	EITEM	OXM_WINDOWOPEN
	EITEM	OXM_WINDOWCLOSING

   	EITEM	OXM_TABCHAIN	; link all interactive elements in a ring for
				; prev/next selection via tab
	EITEM	OXM_INVISIBLE
	EITEM	OXM_VISIBLE

	EITEM	OXM_APPWINMESSAGE
	EITEM	OXM_REFRESH

	EITEM	OXM_NEWPENS
	EITEM	OXM_INHERIT

	EITEM	OXM_ATTRSDONE	; this message (method) is sent after all
				; inital attribute tags have been set
				; this is usefull for example for creating co-objects,
				; like for example the grid, image and text in a button 

	EITEM	OXM_NEXT	; step to next/prev object in tabulator-chain
	EITEM	OXM_PREV	; this is required if a gadget hast multiple active areas,
				; like the multiple handles of a tabs gadget
	EITEM	OXM_ISCHILD

	EITEM	OXM_GETCLIP

	EITEM	OXM_HOTKEY	; if the class attribute oxCA_autohotkey is set to FALSE,
				; this method is sent to objects when their hoteky is pressed
				; (see class attributes)

---

.i code:

---

; object interconnection for use with oxNotify() / oxNotifyAttr()
; ---------------------------------------------------------------
;
; the difference between OX_BIND and OX_NOTIFY is, that one object may
; have multiple notifys but only one binding and that oxNotifyAttr()
; yet only works with notifys.
;
; OX_BIND makes a chain, where every object in the chain will get the
; message sent with oxNotify(). you must make a ring with OX_BIND in
; order to get a message read by all objects in the chain regardless
; of where you start it.
;
; OX_NOTIFY makes multiple destinations, but the message or attr is not
; sent further.
;
; you can use both the OX_BIND and the OX_NOTIFY(s) on one object, but
; OX_BIND works only once.

	XITEM	OX_NOTIFY		; generate notify from one object to annother, tag_data should
					; point to a taglist as shown below

	XITEM	OX_BIND			; bind one object to annother and back, the OX_BIND tag must be
					; followed by a pointer to a pointer where the address of the
					; destination object is stored with OX_PUTPTR or OX_RELPTR.

OX_REL		EQU	$00000001	; odd pointers in tag_data are offsets to current userbase  that
					; is active at the moment of creation (odd bit masked out)

; attributes for OX_NOTIFY:

	ENUM	$1000

	EITEM	oxNA_Target		; pointer to a pointer to destination object

	EITEM	oxNA_MatchAttr		; attribute to catch
	EITEM	oxNA_NewAttr		; attribute to send in place of the catched one
					; if this is not given, match attr is sent as is

	EITEM	oxNA_Hook		; attach a callback-hook to a widget to receive
					; everything that is sent through Notify() / NotifyAttr()
					; hook gets: a0/a3 object, a1 message, a4 base, a6 oxbase
					; the message is allways a method. if it comes from
					; NotifyAttr(), the message is OXM_SET and (a1) is attr, value

---