Problem with WB3D_Spinner?

Blitz3D Forums/Blitz3D Programming/Problem with WB3D_Spinner?

Guy Fawkes

(Posted 2012) [#1]

Hi all. Can someone please tell me why I can't get these spinners to go up by .01 or down by .01? I need it so that I can go up or down an entity's X,Y,Z position.

Here's the code:

WB3DStyles.bb:

;
; WB3DStyles Copyright Kevin Poole, 2006
;	


; internal winblitz3d gadget events
Const WB3D_EVENT_GADGET						= $401
Const WB3D_EVENT_MENU						= $1001
Const WB3D_EVENT_MOUSEWHEEL					= $208
Const WB3D_EVENT_WINDOW_CLOSE				= $803
Const WB3D_EVENT_WINDOW_SIZE				= $802
Const WB3D_EVENT_WINDOW_SIZEING				= $805
Const WB3D_EVENT_WINDOW_MOVE				= $807
Const WB3D_EVENT_WINDOW_MOVING				= $806
Const WB3D_EVENT_MOUSE_MOVE					= $200
Const WB3D_EVENT_KEYPRESS					= $101
Const WB3D_EVENT_CONTEXTMENU				= $502
Const WB3D_EVENT_SYSTEMTRAY					= $503
Const WB3D_EVENT_DRAGDROP					= $504
Const WB3D_EVENT_MOUSE_DOWN 				= $201 

; winblitz3d key press events, these are standard VK_ winapi constants.
Const WB3D_KEY_ENTER 						= $D
Const WB3D_KEY_TAB							= 9
Const WB3D_KEY_SHIFT 						= $10
Const WB3D_KEY_CONTROL 						= 17
Const WB3D_KEY_ESCAPE 						= 27
Const WB3D_KEY_SPACE 						= $20
Const WB3D_KEY_END 							= 35
Const WB3D_KEY_HOME 						= 36
Const WB3D_KEY_CURS_LEFT 					= 37
Const WB3D_KEY_CURS_UP 						= 38
Const WB3D_KEY_CURS_RIGHT 					= 39
Const WB3D_KEY_DOWN 						= 40
Const WB3D_KEY_INSERT 						= 45
Const WB3D_KEY_DELETE 						= 46
Const WB3D_KEY_NUMPAD0 						= 96
Const WB3D_KEY_NUMPAD1 						= 97
Const WB3D_KEY_NUMPAD2 						= 98
Const WB3D_KEY_NUMPAD3 						= 99
Const WB3D_KEY_NUMPAD4 						= 100
Const WB3D_KEY_NUMPAD5 						= 101
Const WB3D_KEY_NUMPAD6 						= 102
Const WB3D_KEY_NUMPAD7 						= 103
Const WB3D_KEY_NUMPAD8 						= 104
Const WB3D_KEY_NUMPAD9 						= 105
Const WB3D_KEY_F1 							= 112
Const WB3D_KEY_F2 							= 113
Const WB3D_KEY_F3 							= 114
Const WB3D_KEY_F4 							= 115
Const WB3D_KEY_F5 							= 116
Const WB3D_KEY_F6 							= 117
Const WB3D_KEY_F7 							= 118
Const WB3D_KEY_F8 							= 119
Const WB3D_KEY_F9 							= 120
Const WB3D_KEY_F10 							= 121
Const WB3D_KEY_F11 							= 122
Const WB3D_KEY_F12 							= 123
Const WB3D_KEY_NUMLOCK 						= 144
Const WB3D_KEY_SCROLL 						= 145


; default toolbar buttons
Const STD_COPY 								= 1
Const STD_CUT 								= 0
Const STD_DELETE 							= 5
Const STD_FILENEW 							= 6
Const STD_FILEOPEN 							= 7
Const STD_FILESAVE 							= 8
Const STD_FIND 								= 12
Const STD_HELP 								= 11
Const STD_PASTE 							= 2
Const STD_PRINT 							= 14
Const STD_PRINTPRE 							= 9
Const STD_PROPERTIES 						= 10

; standard window constants
Const WS_CHILD 								= $40000000
Const WS_VISIBLE 							= $10000000
Const WS_ACTIVECAPTION 						= 1
Const WS_BORDER 							= $800000
Const WS_CAPTION 							= $C00000
Const WS_CLIPCHILDREN 						= $2000000
Const WS_CLIPSIBLINGS 						= $4000000
Const WS_DISABLED 							= $8000000
Const WS_GROUP 								= $20000
Const WS_HSCROLL 							= $100000
Const WS_MAXIMIZE 							= $1000000
Const WS_MINIMIZE 							= $20000000
Const WS_MAXIMIZEBOX 						= $10000
Const WS_MINIMIZEBOX 						= $20000
Const WS_OVERLAPPED 						= 0
Const WS_POPUP 								= $80000000
Const WS_SYSMENU 							= $80000
Const WS_TABSTOP 							= $10000
Const WS_THICKFRAME 						= $40000
Const WS_VSCROLL 							= $200000
Const WS_ICONIC 							= WS_MINIMIZE
Const WS_TILED 								= WS_OVERLAPPED
Const WS_GT 								= WS_GROUP Or WS_TABSTOP
Const WS_SIZEBOX 							= WS_THICKFRAME
Const WS_POPUPWINDOW 						= WS_POPUP Or WS_BORDER Or WS_SYSMENU
Const WS_OVERLAPPEDWINDOW 					= WS_OVERLAPPED Or WS_CAPTION Or WS_SYSMENU Or WS_THICKFRAME Or WS_MINIMIZEBOX Or WS_MAXIMIZEBOX
Const WS_TILEDWINDOW 						= WS_OVERLAPPEDWINDOW
Const WS_DLGFRAME 							= $400000

; window extended winapi styles
Const WS_EX_ACCEPTFILES 					= $10
Const WS_EX_APPWINDOW 						= $40000
Const WS_EX_CLIENTEDGE 						= $200
Const WS_EX_CONTEXTHELP 					= $400
Const WS_EX_CONTROLPARENT 					= $10000
Const WS_EX_LAYERED 						= $80000
Const WS_EX_LAYOUTRTL 						= $400000
Const WS_EX_LEFT 							= 0
Const WS_EX_LEFTSCROLLBAR 					= $4000
Const WS_EX_LTRREADING 						= 0
Const WS_EX_NOACTIVATE 						= $8000000
Const WS_EX_NOINHERITLAYOUT 				= $100000
Const WS_EX_NOPARENTNOTIFY					= $4
Const WS_EX_RIGHT 							= $1000
Const WS_EX_RIGHTSCROLLBAR 					= $0
Const WS_EX_RTLREADING 						= $2000
Const WS_EX_STATICEDGE 						= $20000
Const WS_EX_TOOLWINDOW 						= $80
Const WS_EX_TOPMOST 						= $8
Const WS_EX_TRANSPARENT 					= $20
Const WS_EX_WINDOWEDGE 						= $100
Const WS_EX_DLGMODALFRAME 					= 1
Const WS_EX_PALETTEWINDOW 					= WS_EX_WINDOWEDGE Or WS_EX_TOOLWINDOW Or WS_EX_TOPMOST
Const WS_EX_OVERLAPPEDWINDOW 				= WS_EX_WINDOWEDGE Or WS_EX_CLIENTEDGE

; standard winapi button styles
Const BS_NULL 		 						= 1
Const BS_3STATE 							= 5
Const BS_AUTO3STATE  						= 6
Const BS_AUTOCHECKBOX 						= 3
Const BS_AUTORADIOBUTTON  					= $9
Const BS_BITMAP  							= $80
Const BS_BOTTOM  							= $800
Const BS_CENTER  							= $300
Const BS_CHECKBOX  							= 2
Const BS_DEFPUSHBUTTON  					= 1
Const BS_DIBPATTERN 						= 5
Const BS_DIBPATTERN8X8  					= 8
Const BS_DIBPATTERNPT  						= 6
Const BS_FLAT  								= $8000
Const BS_GROUPBOX  							= $7
Const BS_HOLLOW  							= BS_NULL
Const BS_ICON  								= $40
Const BS_INDEXED  							= 4
Const BS_LEFT  								= $100
Const BS_LEFTTEXT  							= $20
Const BS_MONOPATTERN  						= 9
Const BS_MULTILINE 							= $2000
Const BS_NOTIFY 							= $4000
Const BS_PUSHBUTTON 						= 0
Const BS_PUSHLIKE  							= $1000
Const BS_RADIOBUTTON  						= 4
Const BS_RIGHT 								= $200
Const BS_RIGHTBUTTON  						= BS_LEFTTEXT
Const BS_SOLID  							= 0
Const BS_TEXT  								= 0
Const BS_TOP  								= $400


; toolbar standard winapi styles
Const CCS_ADJUSTABLE 						= $20
Const CCS_BOTTOM 		 					= 3
Const CCS_TOP 								= 1
Const CCS_VERT 							 	= $80
Const CCS_LEFT 								= (CCS_VERT Or CCS_TOP)
Const CCS_NODIVIDER 						= $40
Const CCS_NOMOVEY 							= 2
Const CCS_NOMOVEX 							= (CCS_VERT Or CCS_NOMOVEY)
Const CCS_NOPARENTALIGN 					= 8
Const CCS_NORESIZE 							= 4
Const CCS_RIGHT 							= (CCS_VERT Or CCS_BOTTOM)
Const TBSTATE_CHECKED 						= 1
Const TBSTATE_ELLIPSES 						= $40
Const TBSTATE_ENABLED 						= 4
Const TBSTATE_HIDDEN  						= 8
Const TBSTATE_INDETERMINATE 				= $10
Const TBSTATE_MARKED  						= $80
Const TBSTATE_PRESSED 						= $2
Const TBSTATE_WRAP 							= $20
Const TBSTYLE_ALTDRAG 						= $400
Const TBSTYLE_AUTOSIZE 						= $10
Const TBSTYLE_BUTTON 						= 0
Const TBSTYLE_CHECK 						= 2
Const TBSTYLE_GROUP 						= 4
Const TBSTYLE_CHECKGROUP 					= (TBSTYLE_GROUP Or TBSTYLE_CHECK)
Const TBSTYLE_CUSTOMERASE 					= $2000
Const TBSTYLE_DROPDOWN 						= 8
Const TBSTYLE_FLAT 							= $800
Const TBSTYLE_LIST 							= $1000
Const TBSTYLE_NOPREFIX 						= $20
Const TBSTYLE_REGISTERDROP 					= $4000
Const TBSTYLE_SEP 							= 1
Const TBSTYLE_TOOLTIPS 						= $100
Const TBSTYLE_TRANSPARENT 					= $8000
Const TBSTYLE_WRAPABLE 		 				= $200

; toolbar extended winapi styles
Const TBSTYLE_EX_DOUBLEBUFFER 				= $80
Const TBSTYLE_EX_DRAWDDARROWS 				= $1
Const TBSTYLE_EX_HIDECLIPPEDBUTTONS 		= $10
Const TBSTYLE_EX_MIXEDBUTTONS 				= $8

; standard textarea/editfield winapi styles
Const ES_AUTOHSCROLL 		 				= $80
Const ES_AUTOVSCROLL 						= $40
Const ES_CENTER 							= 1
Const ES_CONTINUOUS 						= $80000000
Const ES_DISABLENOSCROLL 					= $2000
Const ES_DISPLAY_REQUIRED 					= 2
Const ES_EX_NOCALLOLEINIT 					= $1000000
Const ES_LEFT 								= 0
Const ES_LOWERCASE 							= $10
Const ES_MULTILINE 							= 4
Const ES_NOHIDESEL 							= $100
Const ES_NOIME 								= $80000
Const ES_NOOLEDRAGDROP 						= $8
Const ES_NUMBER 							= $2000
Const ES_OEMCONVERT 						= $400
Const ES_PASSWORD 							= $20
Const ES_READONLY 							= $800
Const ES_RIGHT 								= 2
Const ES_SAVESEL 							= $8000
Const ES_SELECTIONBAR 						= $1000000
Const ES_SELFIME 							= $40000
Const ES_SUNKEN 							= $4000
Const ES_SYSTEM_REQUIRED 					= 1
Const ES_UPPERCASE 							= $8
Const ES_USER_PRESENT 						= 4
Const ES_VERTICAL 							= $400000
Const ES_WANTRETURN 						= $1000

; standard combobox winapi styles
Const CBS_AUTOHSCROLL 						= $40
Const CBS_DISABLENOSCROLL 					= $800
Const CBS_DROPDOWN 							= 2
Const CBS_DROPDOWNLIST 						= 3
Const CBS_HASSTRINGS 						= $200
Const CBS_LOWERCASE 						= $4000
Const CBS_NOINTEGRALHEIGHT 					= $400
Const CBS_OEMCONVERT 						= $80
Const CBS_SIMPLE 							= 1
Const CBS_SORT 								= $100
Const CBS_UPPERCASE 						= $2000

; standard tabber winapi styles
Const TCS_MULTILINE 						= $200
Const TCS_SINGLELINE 						= $0
Const TCS_FLATBUTTONS 						= $8
Const TCS_BOTTOM 							= $2
Const TCS_HOTTRACK 							= $40
Const TCS_RAGGEDRIGHT 						= $800
Const TCS_VERTICAL 							= $80
Const TCS_FOCUSONBUTTONDOWN 				= $1000
Const TCS_BUTTONS 							= $100
Const TCS_FIXEDWIDTH 						= $400
Const TCS_FOCUSNEVER 						= $8000
Const TCS_FORCEICONLEFT 					= $10
Const TCS_FORCELABELLEFT 					= $20
Const TCS_MULTISELECT 						= 4
Const TCS_RIGHT 							= 2
Const TCS_RIGHTJUSTIFY 						= 0
Const TCS_SCROLLOPPOSITE 					= 1
Const TCS_TABS 								= 0
Const TCS_TOOLTIPS 							= $4000

; tabber extended styles
Const TCS_EX_FLATSEPARATORS 				= 1
Const TCS_EX_REGISTERDROP 					= 2

; standard listview/listbox winapi styles
Const LVS_ALIGNLEFT 						= $800
Const LVS_ALIGNMASK 						= $c00
Const LVS_ALIGNTOP 							= 0
Const LVS_AUTOARRANGE						= $100
Const LVS_EDITLABELS 						= $200
Const LVS_ICON 								= 0
Const LVS_LIST 								= 3
Const LVS_NOCOLUMNHEADER 					= $4000
Const LVS_NOLABELWRAP 						= $80
Const LVS_NOSCROLL 							= $2000
Const LVS_NOSORTHEADER 						= $8000
Const LVS_REPORT 							= 1
Const LVS_SHOWSELALWAYS 					= $8
Const LVS_SINGLESEL 						= 4
Const LVS_SMALLICON 						= 2
Const LVS_SORTASCENDING 					= $10
Const LVS_SORTDESCENDING 					= $20
Const LVS_TYPEMASK 							= 3
Const LVS_TYPESTYLEMASK 					= $fc00

; listview extended styles
Const LVS_EX_FULLROWSELECT 					= $20
Const LVS_EX_GRIDLINES 						= 1
Const LVS_EX_BORDERSELECT 					= $8000
Const LVS_EX_CHECKBOXES 					= 4
Const LVS_EX_DOUBLEBUFFER 					= $10000
Const LVS_EX_FLATSB 						= $100
Const LVS_EX_HEADERDRAGDROP 				= $10
Const LVS_EX_HIDELABELS 					= $20000
Const LVS_EX_INFOTIP 						= $400
Const LVS_EX_LABELTIP 						= $4000
Const LVS_EX_MULTIWORKAREAS 				= $2000
Const LVS_EX_ONECLICKACTIVATE 				= $40
Const LVS_EX_REGIONAL 						= $200
Const LVS_EX_SINGLEROW 						= $40000
Const LVS_EX_SNAPTOGRID 					= $80000
Const LVS_EX_SUBITEMIMAGES 					= 2
Const LVS_EX_TRACKSELECT 					= $8
Const LVS_EX_TWOCLICKACTIVATE 				= $80
Const LVS_EX_UNDERLINECOLD 					= $1000
Const LVS_EX_UNDERLINEHOT 					= $800

; standard progressbar winapi styles
Const PBS_SMOOTH 							= 1
Const PBS_VERTICAL 							= 4

; standard treeview winapi styles
Const TVS_CHECKBOXES 						= $100
Const TVS_DISABLEDRAGDROP 					= $10
Const TVS_EDITLABELS 						= $8
Const TVS_FULLROWSELECT 					= $1000
Const TVS_HASBUTTONS 						= 1
Const TVS_HASLINES 							= 2
Const TVS_INFOTIP 							= $800
Const TVS_LINESATROOT 						= 4
Const TVS_NOHSCROLL 						= $8000
Const TVS_NONEVENHEIGHT 					= $4000
Const TVS_NOSCROLL 							= $2000
Const TVS_NOTOOLTIPS 						= $80
Const TVS_RTLREADING 						= $40
Const TVS_SHOWSELALWAYS 					= $20
Const TVS_SINGLEEXPAND 						= $400
Const TVS_TRACKSELECT 						= $200

; standard label winapi styles
Const SS_BITMAP 							= $E
Const SS_BLACKFRAME 						= $7
Const SS_BLACKRECT 							= 4
Const SS_CENTER 							= 1
Const SS_CENTERIMAGE 						= $200
Const SS_ELLIPSISMASK 						= $C000
Const SS_ENDELLIPSIS 						= $4000
Const SS_ENHMETAFILE 						= $F
Const SS_ETCHEDFRAME 						= $12
Const SS_ETCHEDHORZ 						= $10
Const SS_ETCHEDVERT 						= $11
Const SS_GRAYFRAME 							= $8
Const SS_GRAYRECT 							= $5
Const SS_ICON 								= $3
Const SS_LEFT 								= 0
Const SS_LEFTNOWORDWRAP 					= $C
Const SS_SIMPLE 							= $B
Const SS_SUNKEN 							= $1000
Const SS_WHITEFRAME 						= $9
Const SS_WHITERECT 							= $6
Const SS_WORDELLIPSIS 						= $C000
Const SS_NOTIFY								= $100
Const SS_RIGHT 								= $2 

; standard trackbar winapi styles
Const TBS_AUTOTICKS 						= 1
Const TBS_BOTH 								= 8
Const TBS_BOTTOM 							= 0
Const TBS_ENABLESELRANGE 					= $20
Const TBS_FIXEDLENGTH 						= $40
Const TBS_HORZ 		 						= 0
Const TBS_LEFT 								= 4
Const TBS_NOTHUMB 							= $80
Const TBS_NOTICKS 							= $10
Const TBS_REVERSED 							= $200
Const TBS_RIGHT 							= 0
Const TBS_TOP 								= 4
Const TBS_VERT 								= 2

; standard spinner winapi styles, Aka up-down controls
Const UDS_ALIGNLEFT 						= $8
Const UDS_ALIGNRIGHT 						= 4
Const UDS_ARROWKEYS 						= $20
Const UDS_AUTOBUDDY 						= $10
Const UDS_HORZ 								= $40
Const UDS_HOTTRACK 							= $100
Const UDS_NOTHOUSANDS 						= $80
Const UDS_SETBUDDYINT 						= 2
Const UDS_WRAP 								= 1

; standard messagebox winapi styles, Aka Notify control
Const MB_ABORTRETRYIGNORE 					= $2
Const MB_APPLMODAL 							= $0
Const MB_CANCELTRYCONTINUE 					= $6
Const MB_COMPOSITE 							= $2
Const MB_DEFAULT_DESKTOP_ONLY 				= $20000
Const MB_DEFBUTTON1 						= 0
Const MB_DEFBUTTON2 						= $100
Const MB_DEFBUTTON3 						= $200
Const MB_DEFBUTTON4 						= $300
Const MB_DEFMASK 							= $F00
Const MB_HELP 								= $4000
Const MB_ICONASTERISK 						= $40
Const MB_ICONEXCLAMATION 					= $30
Const MB_ICONHAND 							= $10
Const MB_ICONERROR 							= MB_ICONHAND
Const MB_ICONINFORMATION 					= MB_ICONASTERISK
Const MB_ICONMASK 							= $F0
Const MB_ICONQUESTION 						= $20
Const MB_ICONSTOP 							= MB_ICONHAND
Const MB_ICONWARNING 						= MB_ICONEXCLAMATION
Const MB_MISCMASK 							= $C000
Const MB_MODEMASK 							= $3000
Const MB_NOFOCUS 							= $8000
Const MB_OK 								= $0
Const MB_OKCANCEL 							= $1
Const MB_PRECOMPOSED 						= $1
Const MB_RETRYCANCEL 						= $5
Const MB_RIGHT 								= $80000
Const MB_RTLREADING 						= $100000
Const MB_SETFOREGROUND 						= $10000
Const MB_SYSTEMMODAL 						= $1000
Const MB_TASKMODAL 							= $2000
Const MB_TOPMOST 							= $40000
Const MB_TYPEMASK 							= $F
Const MB_USERICON 							= $80
Const MB_YESNO 								= 4
Const MB_YESNOCANCEL 						= 3

; standard messagebox winapi return values
Const IDABORT								= 3				; Abort button was selected.
Const IDCANCEL								= 2				; Cancel button was selected.
Const IDIGNORE								= 5				; Ignore button was selected.
Const IDNO									= 7				; No button was selected.
Const IDOK									= 1				; OK button was selected.
Const IDRETRY								= 4				; Retry button was selected.
Const IDYES									= 6 			; Yes button was selected.
Const IDCONTINUE 							= 11			; Continue button selected.
Const IDCLOSE 								= 8				; Close button selected
Const IDHELP 								= 9				; Help button selected.
Const IDTRYAGAIN 							= 10			; Try again selected.

;Window Messages

Const WM_PAINT                              = $000F         ;Refresh the window on the screen
Const WM_MOVING                             = $0216         ;Stop Window from being dragged

; converts a blitz image to a wb3d icon. 
Function WB3D_BBImageToIcon(image) 

Local offset = 0 

If image = 0 Then Return 0 

; create an icon bank to store rgba values 
icon=CreateBank((ImageWidth(image)*ImageHeight(image))*4) 

;lock the buffer for fast access. 
oldBuffer=GraphicsBuffer() ;Remember the previous buffer, though 
SetBuffer ImageBuffer(image) 

; get the images rgba data and copy it to the bank. 
LockBuffer 
For y = ImageHeight(image)-1 To 0 Step-1 
For x = 0 To ImageWidth(image)-1 
PokeInt icon, offset, ReadPixelFast(x,y) 
offset=offset+4 
Next 
Next 
UnlockBuffer 

SetBuffer(oldBuffer) ;Revert to the old buffer 

; convert the rgb image data to an icon. 
Converted_Icon = WB3D_ConvertBlitzImage(icon,ImageWidth(image),ImageHeight(image),BankSize(icon)) 
FreeBank icon 

; return the created icon. 
Return Converted_Icon 

End Function

Spinners.bb:

Graphics3D 800, 600, 0, 2

Global title$ = "Spinner Example - V.1.0 (Beta)"

AppTitle title$

Global metricwidth% = api_GetSystemMetrics(0)
Global metricheight% = api_GetSystemMetrics(1)

Global middlexpos% = metricwidth%/2-GraphicsWidth()/2
Global middleypos% = metricheight%/2-GraphicsHeight()/2


Include "WB3DStyles.bb"


;Globals
Global DesktopW=api_GetSystemMetrics(0)
Global DesktopH=api_GetSystemMetrics(1)
Global WindowW=GraphicsWidth()
Global WindowH=GraphicsHeight()
Global WindowX=(DesktopW-WindowW)/2
Global WindowY=(DesktopH-WindowH)/2

Global winMain

Global w2

Global h2

Global QUIT

Global RuntimeWindow_hWnd = WB3D_InitializeGUI(SystemProperty("AppHwnd"),0,0,GraphicsWidth(),GraphicsHeight())
api_MoveWindow% (RuntimeWindow_hWnd, middlexpos%, middleypos%, GraphicsWidth(), GraphicsHeight(), WM_PAINT)
WB3D_DragAcceptFiles RuntimeWindow_hWnd,True

Global ControlPanel = WB3D_CreateWindow("Control Menu", 0, 0, 250, GraphicsHeight()-48, Runtimewindow_hWnd, 0)
api_MoveWindow% (ControlPanel, 0, 0, 250, GraphicsHeight()-48, WM_PAINT)

Global XPos_Label = WB3D_CreateLabel("X: ", 10, 20, 25, 20, ControlPanel, WS_CHILD)
Global YPos_Label = WB3D_CreateLabel("Y: ", 10, 60, 25, 20, ControlPanel, WS_CHILD)
Global ZPos_Label = WB3D_CreateLabel("Z: ", 10, 100, 25, 20, ControlPanel, WS_CHILD)

Global xposition_spinnerlabel = WB3D_CreateEditField("0.00",45,17,160,20,ControlPanel,0,WS_CHILD)
Global yposition_spinnerlabel = WB3D_CreateEditField("0.00",45,57,160,20,ControlPanel,0,WS_CHILD)
Global zposition_spinnerlabel = WB3D_CreateEditField("0.00",45,97,160,20,ControlPanel,0,WS_CHILD)

Global xspinner = WB3D_CreateSpinner(31,15,15,23,ControlPanel,0,WS_CHILD Or UDS_NOTHOUSANDS Or UDS_WRAP)
Global yspinner = WB3D_CreateSpinner(31,55,15,23,ControlPanel,0,WS_CHILD Or UDS_NOTHOUSANDS Or UDS_WRAP)
Global zspinner = WB3D_CreateSpinner(31,95,15,23,ControlPanel,0,WS_CHILD Or UDS_NOTHOUSANDS Or UDS_WRAP)

; menus
menus = WB3D_WindowMenu(RuntimeWindow_hWnd)
file = WB3D_CreateMenu("File",0,menus,0)
NewItem = WB3D_CreateMenu("New",1,file,0) 
OpenItem = WB3D_CreateMenu("Open",2,file,0) 

SaveItem = WB3D_CreateMenu("Save",3,file,0)
WB3D_CreateMenu("",0,file,0)
QuitItem = WB3D_CreateMenu("Quit",4,file,0)


WB3D_UpdateWindowMenu(RuntimeWindow_hWnd)


api_SetFocus SystemProperty("ApphWnd")


; cleanup any old creation events, its better to do this before we enter the main
; event loop, when some gadgets are created they generate events.
WB3D_FlushEvents


While Not KeyDown(1) Or QUIT

Cls

SetBuffer BackBuffer()

WB3D_UpdateGUI()

Flip

Wend

WB3D_EndGUI()

End

Function WB3D_UpdateGUI()	

	If QUIT = 1 Then WB3D_EndGUI() : End
	
		; get an event of the event queue.
	event = WB3D_WaitEvent()
	
	metricwidth% = api_GetSystemMetrics(0)
	metricheight% = api_GetSystemMetrics(1)
	
	middlexpos% = metricwidth%/2-GraphicsWidth()/2
	middleypos% = metricheight%/2-GraphicsHeight()/2
			
	Select event
		
		Case WB3D_EVENT_GADGET			
			Select WB3D_EventSource()

			
				Case xspinner
					 count=count+1
					 WB3D_SetGadgetText(xspinner,count)
			End Select

			
		Case $805
			api_MoveWindow% (RuntimeWindow_hWnd, middlexpos%, middleypos%, GraphicsWidth(), GraphicsHeight(), wm_paint)
			api_MoveWindow% (ControlPanel, 0, 0, 250, GraphicsHeight()-48, WM_PAINT)
			
		Case $806
			api_MoveWindow% (RuntimeWindow_hWnd, middlexpos%, middleypos%, GraphicsWidth(), GraphicsHeight(), wm_paint)	
			api_MoveWindow% (ControlPanel, 0, 0, 250, GraphicsHeight()-48, WM_PAINT)
			
		Case $807
			api_MoveWindow% (RuntimeWindow_hWnd, middlexpos%, middleypos%, GraphicsWidth(), GraphicsHeight(), wm_paint)
			api_MoveWindow% (ControlPanel, 0, 0, 250, GraphicsHeight()-48, WM_PAINT)
			
						
			
		Case WB3D_EVENT_MENU
			Select WB3D_EventData()
					
				Case 1
					WB3D_Notify "Menu","You selected 'New' menu item",0
					
				Case 2
					WB3D_Notify "Menu","You selected 'Open' menu item",0
					
				Case 3
					WB3D_Notify "Menu","You selected 'Save' menu item",0
					
				Case 4
					QUIT = 1
			End Select
			
			
		Case WB3D_EVENT_WINDOW_CLOSE
			
			Select WB3D_EventSource()
				Case RuntimeWindow_hWnd
					WB3D_EndGUI()
					ClearWorld(1, 1, 1)
					End
					
					
			End Select
			
			
		Case WB3D_EVENT_DRAGDROP
			
			Select WB3D_EventSource()	
					
				Case RuntimeWindow_hWnd
					
					
					
					For do_files = 0 To WB3D_CountDroppedFiles()
		                file1$ = WB3D_DroppedFileName(do_files)
						api_MessageBox(0, file1$, file1$, 0)
					Next
					
					
			End Select		
			
			
	End Select
	
	
	
End Function

Thanks to all that help! :)

Last edited 2012

Yasha

(Posted 2012) [#2]

I won't attempt to answer this right now, because I don't have enough familiarity with WB3D to know what to look for (and... I can't see anything that obviously looks like it's updating a spinner in that code). However...

I would strongly recommend that if you want to make a Windows GUI app, you not use Blitz3D. The style of programming forced on you by certain antifeatures of the Blitz language makes it impossible to program a GUI in an idiomatic way (instead you have to do that WaitEvent nonsense), so nothing you learn from this will be of any value for general Windows or GUI programming. (If WB3D_WaitEvent works the way I think it does, it will also interfere with 3D scenes updating properly.)

If you want your app to be primarily 3D, feel free to use B3D but design the 3D content first, and tack a GUI on top of more generic inputs using as thin a layer as possible so that it doesn't affect your program's logic.

If the 3D is just a helper for a primarily GUI app, B3D is definitely the wrong tool for the job, and you should use something else.

Guy Fawkes

(Posted 2012) [#3]

Im not giving up.

Yasha

(Posted 2012) [#4]

Well, actually you are.

When there is no merit in continuing a course of action, and you insist on following it anyway for what appears to be no reason, then yes, you have given up on succeeding in favour of... I have no idea what. Certainly not virtue. Whoever taught you not to give up even when you're doing it wrong did you a great disservice.

Guy Fawkes

(Posted 2012) [#5]

Regardless of ur smart alec remarks, I am NOT giving up :) Also, NICE PEOPLE ONLY, allowed in here. If ur not gonna be nice then please, have a nice day! And go somewhere else! Otherwise, stay here, and be nice :) Thank You! :)

Yasha

(Posted 2012) [#6]

My comments were well-intentioned, thank you very much.

Now, consider carefully: why do you not want to "give up" on something you've just been told is fruitless, having little practical and zero educational value?

You aren't being persistent, or plucky: you're being stubborn and foolish and you don't even have a reason.

Fine, if you're determined to find ways to waste your own effort, do your own damn thing.

ando	(Posted 2012) [#7]

.....

Last edited 2012

_PJ_	(Posted 2012) [#8]

Yet again you've copied & pasted someone else's code and are now trying to make use of it without a clue how it works...

However, I'll provide some way towards the answer you want:

1) Restore the code functionality from the original which deals with event messages from the gadgets
2) Especially those for "Spinner " type gadgets

3) (This is the main part)
Either remember to set a coefficient to divide the spinner value by 100 or so...
OR
Ensure that the spinner's value is able to take a Float and that increment/decrements are in the order 0.1

Guy Fawkes

(Posted 2012) [#9]

Yasha, please leave. u are not welcome here. Ur rudeness has taken its toll. Ando, Im TRYING to be nice, but they arent helping.

PJ, I have NOT copy and pasted this.. I made this myself. Stop ASSUMING i copied... -.-

Yasha

(Posted 2012) [#10]

Yasha, please leave. u are not welcome here. Ur rudeness has taken its toll

When, precisely? The part where I tried to be helpful or the part where I tried to reason through why you repeatedly refuse to even read sensible advice? (You shouldn't be designing a Windows GUI app in B3D, it's a terrible idea!)

I was prepared - I am still prepared - to give you a lot of help, but your only response to anything that isn't a complete prepared copy-paste solution seems to be incoherent rage, exactly as it has been for the last two years (you really do never change, do you? Take heed ando, this is an ancient dance).

You don't have to take my advice - you don't even have to acknowledge it - but if you're going to accuse me of rudeness you could have the basic decency to actually read my comments and try to understand them first (perhaps by asking for clarification as to e.g. why I think idiomatic GUI programming is so hard in B3D).

Guy Fawkes

(Posted 2012) [#11]

I will NOT put up with rudeness anymore. Yes, I am willing to listen to what u have to say. IF u are kind while saying it. Otherwise, u are a fly on the wall.

Ross C

(Posted 2012) [#12]

Get a grip dude!. Yasha is a good guy to have on your side when it comes to helping with coding. Don't be rude to him. How do you know it's not his birthday today? Happy Birthday Yasha (if it's your birthday that is).

Guy Fawkes

(Posted 2012) [#13]

Ross. Quit hijacking my threads. Either make ur own, or go away. IM not the one being rude to him at ALL. HES the one being rude to ME. It WAS my birthday 2 days ago.

Yasha

(Posted 2012) [#14]

Sadly not my birthday, no.

I will forgo explaining in detail for the moment, but I believe the program should be redesigned (or, y'know, designed). How it should be redesigned depends on what it's supposed to be, because the different tools at our disposal are best used in different ways.

So, going back to the first question: is this a primarily 3D app with a thin GUI control layer over the top, or a primarily GUI app with a few 3D bits? Or does it make heavy but equal use of both? Or some other combination? The answer to this question will provide you with a starting point for best design.

I was actually working on not even one but two tools to ease designing this sort of thing in B3D! I should probably do some more on them, then I can recommend simple alternatives...

(Tip: If you don't want design help at this stage, just say "no, I am confident that the design of my application is adequate for my needs at the moment" or something that's a little more sensible and thought-through than "Nevar give up!", and foosh the Yasha-genie disappears again.)

Last edited 2012

Guy Fawkes

(Posted 2012) [#15]

It's a Particle Editor for Particle Candy. I HATE the old one they made a long time ago. It's like a Level Editor for Particles

Yasha

(Posted 2012) [#16]

I'm actually going to take a moment to commend your choice of project here. A particle editor is a great idea as a beginner's application project (kinda like pong would be as a beginner's game project): it's small, so it's within your ability to complete; it's clearly-defined, so you won't be subject to overdesign or feature-creep; and it's of practical value, so you can take pleasure in a tool you made with your own hands. Well done! You did learn something!

Now it looks like the main part of your project is actually the GUI section, since the mechanical problem is already solved and your main issue is that you don't like CandyStore's interface, right? (I actually really liked CandyStore, but w/e, each to their own.)

However, because this is such a clearly-defined small project, I would recommend that you leave the GUI for the moment and focus on the rest of it first (design the GUI on paper or a prototyping app if you like, but don't write the code yet).

Consider your application as a whole. As a particle editor, it has four main tasks it needs to fulfil:

-- maintain a model of the particle effect currently being edited
-- allow the user to apply changes to that particle effect model
-- display the current particle effect through Particle Candy
-- save the effect model to a file that can later be loaded by your main project (offhand I can't remember how Particle Candy loads effects... I assume there is some established method).

Each of these is really a separate task. Note that as yet, none of them say anything about the nature of the interface the user actually goes through to make changes.

So. The most fundamental of these is the effect model. This doesn't really need to be anything more complicated than a collection of variables, each representing one of the properties you want to be able to edit (note: this does not need to match up with Particle Candy's internal particle properties: this is about what properties you want a particle to have and to be able to adjust). You could use a bunch of globals for this, or better, and instance of a custom record type representing "an effect". So all the model is is a list of numbers describing the editable properties of your particle effect.

Everything revolves around the model (functionality of the app will be all about this set of properties, so settling on them is absolutely fundamental), so this should be what you design first. At this point I would recommend breaking away, designing a particle-model-module, and having it load a list of properties and display them onscreen as text/numbers, just to check that you can hold and modify the effect model as a thing in itself.

Once that's done, you should create a proper code interface for manipulating it. Create a function for each property that lets you either set or adjust it (set-to-new-value or add-this-to-existing-value), and rebuild your app to use these functions and these functions only to manipulate the model. The core of your application is now in place. (Still haven't looked at the GUI.)

...if this is making sense or sounding familiar so far, then you should be able to see where the rest of the design goes, and why the GUI shouldn't be providing a base architecture for the rest of your program. As long as each section can communicate with each other only though predefined channels: the main draw loop asks Particle Candy to read from the effect model and translate your useful-properties into Particle Candy-specific-properties, then draw them; the control section of the loop should take effect-control events and apply them to your effect-model-control functions; and only these effect-control-events should be generated by the GUI which has translated them out of actual GUI inputs.

It sounds like a lot of complication, but believe me when I say it's easier than trying to intermingle GUI code and functionality code.

More importantly, it means you can build in stages: after you have the text-on-screen version of your effect model, you can build the draw loop which uses Particle Candy to draw the particle effect without thinking about how the user will control this. Drawing then takes care of itself, and you can test the particle effect management by having text on screen showing you numbers, and having simple key presses generating effect control events.

Then, once you have the editor essentially working (i.e. able to edit particle effects and display them in action), you can create a GUI layer that doesn't really "do" anything, but instead simply generates effect-control events to pass on to the model, which will in turn be automatically picked up by the display engine. Because the GUI goes through this translated "channel", you can use it, not use it (and stick to keyboard), swap it out for another one, etc. without affecting your program's functionality.

This is a bit of a vague ramble that still doesn't address why I think B3D is a bad idea for GUI apps (it has to do with the absence of function pointers), but hopefully will be of at least some help, in splitting the painful GUI-code part of your program out of the bit that actually matters (we can get to the intricacies of GUI programming another time).

stayne

(Posted 2012) [#17]

Holy help. You deserve a medal Yasha.

Guy Fawkes

(Posted 2012) [#18]

Well, Particle Candy is easy to load. Its JUST the WB3D GUI spinner part I need help with. Because with THAT fixed, I can use THAT to implement ALL the functions needed to edit, save, etc... A Particle from Particle Candy :)

stayne

(Posted 2012) [#19]

You're going to use a spinner to save?

Guy Fawkes

(Posted 2012) [#20]

no. im going to use a spinner to change the particle's properties, such as emission, chaos, etc..

ando	(Posted 2012) [#21]

.....

Last edited 2012

Zethrax

(Posted 2012) [#22]

Unfortunately this forum doesn't support sending PMs.

ando	(Posted 2012) [#23]

.....

Last edited 2012

H&K	(Posted 2012) [#24]

How can they be contacted on the forum because I don't do emails.(yet) :)

Well do do emails, takes like 5 mins to set up

ando	(Posted 2012) [#25]

.....

Last edited 2012

Guy Fawkes

(Posted 2012) [#26]

Ok, so can someone please.. PLEASE... Tell me how I can get the spinner to work? >< As I said, if I can get THIS to work, then I pretty much have the whole program working...

ando	(Posted 2012) [#27]

.....

Last edited 2012

Guy Fawkes

(Posted 2012) [#28]

..............................

ando	(Posted 2012) [#29]

I'll go and good luck ! :)

Last edited 2012

Guy Fawkes

(Posted 2012) [#30]

Thanks Ando :)

Guy Fawkes

(Posted 2012) [#31]

Can someone PLEASE help me get spinners working? Ugh... Im trying to be nice, but its getting hard again T_T

stayne

(Posted 2012) [#32]

Done! A little oil did the trick.

Guy Fawkes

(Posted 2012) [#33]

Stayne, u are NOT welcome here! Leave this thread and dont come back! If ur not going to be nice, then leave! Have a good day

Last edited 2012

stayne

(Posted 2012) [#34]

You know what is sad, little fella? Search for the word "spinner" in this 3 year old post of yours.

http://blitzmax.com/Community/posts.php?topic=82225#926706

Guy Fawkes

(Posted 2012) [#35]

HA! That was a particle media player. NOT a particle EDITOR. so therefore, it is NOT sad :)

Naughty Alien

(Posted 2012) [#36]

Last edited 2012

Guy Fawkes

(Posted 2012) [#37]

^ =D

Guy Fawkes

(Posted 2012) [#38]

Can u guys PLEASE for the love of science... GET BACK ON TOPIC! O_O

Adam Novagen

(Posted 2012) [#39]

This thread, like so many of its kin before, has devolved into a sorry, pointless mess.

Guy Fawkes

(Posted 2012) [#40]

Adam, ur not welcome here. go hijack someone elses thread. STOP BEING RUDE PPL! Im SICK of ur rudeness. -.- U know who u r.

Now either be nice, or PLEASE leave. LAST time im gonna warn u.

Yasha

(Posted 2012) [#41]

That was a particle media player. NOT a particle EDITOR. so therefore, it is NOT sad

I believe Naughty is trying to say that you should be seeing the common element between the player and the editor, and reusing your own spinner code, since you have apparently solved this problem before. A spinner's just a spinner, regardless of what it controls. The code should be almost identical (Yasha says without looking at it).

How can they be contacted on the forum because I don't do emails.(yet) :)

If you use the "Contact" tab at the top, you will be given a contact form that will send a message to the BRL staff (although if you "don't do email", they can't easily respond to you).

Guy Fawkes

(Posted 2012) [#42]

Ok Yasha, I'll take a look

Kev	(Posted 2012) [#43]

http://www.blitzbasic.com/Community/posts.php?topic=97555#1134365

_PJ_	(Posted 2012) [#44]

PJ, I have NOT copy and pasted this.. I made this myself. Stop ASSUMING i copied... -.-

Sorry, I didn't realise you were the same person as Kev, and that you created both WB3D and the example program that comes with it....

/sarcasm

Anyway I answered your question, but you seem to have chosen to ignore my suggestion. Similarly, you took offence to Yasha's great advice, and even ignored the point that stayne made where you have, indeed previously made a working use of WB3D spinners.

The problem is with your Update function.

Firstly, note that UNDECLARED LOCAL VARIABLES are always initialised to 0 within B3D. So your 'count' variable is fairly redundant.

Included with WB3D is a very useful HELP file which documents each command and its use. The following entry will be of use.

WB3D_GadgetItemText(
int gadget,
int index,
)

As you can also see in the help file, WB3D_SetGadgetText() takes the following parameters:

WB3D_SetGadgetText(
int gadget,
string newtext;
)

Note the parameter for the new value is a STRING.

You will need to clarify the events a little better. Since you have INCREMENT and DECREMENT 'buttons' on the Spinner, but have not identified them in the code.

Lastly, you may want to also associate the EDIT FIELD with the spinner value.