MaxGUI 1.41 Released

BlitzMax Forums/MaxGUI Module/MaxGUI 1.41 Released

SebHoll(Posted 2010) [#1]
Maintenance release MaxGUI 1.41 is now out and includes the following changes:

MaxGUI.MaxGUI 1.32 Release
+ Added WindowStatusText() command.
- Renamed TGadget.SetStatus() to more specific TGadget.SetStatusText().

MaxGUI.FLTKMaxGUI 1.56 Release
+ Added GetStatusText() implementation.
- Added missing Class() methods to TFLTextField and TFLLabel.
- Fixed RequestColor() parameter passing.
- Fixed pasting into textareas to work with WINDOW_ACCEPTFILES flag.

MaxGUI.Win32MaxGUIEx 0.73 Release
+ Added GetStatusText() implementation.

MaxGUI.CocoaMaxGUI 1.53 Release
+ Added GetStatusText() implementation.

The version number bump is because of the change of the SetStatus() method name in TGadget, but also includes a few bug fixes, and includes a long-time missing WindowStatusText() command. :-)


Grisu(Posted 2010) [#2]
3 days and no reply?

Thanks a lot Seb!


MikeHart(Posted 2010) [#3]
Thanks Seb for the improvements and fixes.


xlsior(Posted 2010) [#4]
Thanks


JoshK(Posted 2010) [#5]
Thanks for the update.


GaryV(Posted 2010) [#6]
I missed this, thank you for the update!


degac(Posted 2010) [#7]
First, thanks for the update.

@Skid,@Sebholl

Second, any ideas/plan about MaxGUI now that is 'open'?
(an hint: grid gadget would be very appreciated! :D)
What help (or kind of help) would you like to see?
From where will we download the next update? From BRL's section or we need to look somewhere else?


*(Posted 2010) [#8]
I get
2010-07-31 18:16:23.328 prp029_01.debug[1973:60b] -[NSMenu submenu]: unrecognized selector sent to instance 0x61c290
2010-07-31 18:16:23.331 prp029_01.debug[1973:60b] -[NSMenu submenu]: unrecognized selector sent to instance 0x61c290


According to Brucey this is a MacGUI problem, im running XCode 3.2.3 I dont know if thats the problem. Any ideas?


MacSven(Posted 2010) [#9]
I have Installed the new version.
I i compile my Monitortest Application i got this error.

2010-08-22 16:24:46.413 MoniCheck.debug[641:60b] *** Assertion failure in -[NSMenu itemAtIndex:], /SourceCache/AppKit/AppKit-1038.32/Menus.subproj/NSMenu.m:779
2010-08-22 16:24:46.416 MoniCheck.debug[641:60b] Invalid parameter not satisfying: (index >= 0) && (index < [_itemArray count])

Any idea?

Befor i installed the new BlitzMac + MaxIDE my application compiled correctly.


ima747(Posted 2010) [#10]
did you rebuild modules? if so try rebuilding all modules rather than just changed.


MacSven(Posted 2010) [#11]
Rebuild all modules again, same problem. Installed the BlitzMax 1.40. Same error

i am using this in my source:

For mode:TGraphicsMode=EachIn GraphicsModes()
	width[i]=mode.width
	height[i]=mode.height
	depth[i]=mode.depth
	hertz[i]=mode.hertz
	Print i
	If width[i]=DesktopWidth() And height[i]=DesktopHeight() Then
		AddGadgetItem combobox," "+width[i]+" x "+height[i]+" , "+depth[i]+" Bit , "+hertz[i]+" Hertz",True
		Setscreen=i
	Else
		AddGadgetItem combobox," "+width[i]+" x "+height[i]+" , "+depth[i]+" Bit , "+hertz[i]+" Hertz"
	EndIf
	i:+1
Next


If i remove the AddGadgetItem my application works!


For mode:TGraphicsMode=EachIn GraphicsModes()
	width[i]=mode.width
	height[i]=mode.height
	depth[i]=mode.depth
	hertz[i]=mode.hertz
	Print i
	If width[i]=DesktopWidth() And height[i]=DesktopHeight() Then
		AddGadgetItem combobox,i+" "+width[i]+" x "+height[i]+" , "+depth[i]+" Bit , "+hertz[i]+" Hertz",True
		Setscreen=i
	Else
		AddGadgetItem combobox,i+" "+width[i]+" x "+height[i]+" , "+depth[i]+" Bit , "+hertz[i]+" Hertz"
	EndIf
	i:+1
Next

If i use this code it works too.
Is this a problem then i am using 2 Monitor on my MAC?


skidracer(Posted 2010) [#12]
What does the ,True parameter signify?


ima747(Posted 2010) [#13]
http://www.blitzbasic.com/Community/posts.php?topic=91200
I had the same problem I believe, I reported it in bugs, it's because 2 list items have the exact same text because the graphics modes has a glitch that reports a resolution twice for some reason...

parse your graphics modes to make sure you don't get a double entry (or if you just want to confirm add your "i" variable to the end addgadgetitem text to ensure that every entry is unique) assuming you're finding the same thing I did (was also on dual head mac, my PC didn't seem to have the double resolution).


MacSven(Posted 2010) [#14]
This is my Crash report:


Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 MoniCheck.debug 0x00202d2f collectMem + 283
1 MoniCheck.debug 0x002030b6 bbGCAllocObject + 135
2 MoniCheck.debug 0x00208d6f bbObjectNew + 81
3 MoniCheck.debug 0x00065665 _maxgui_cocoamaxgui_TIntWrapper_Create + 65
4 MoniCheck.debug 0x0005ead3 862 + 11
5 MoniCheck.debug 0x0005ed12 13 + 41
6 MoniCheck.debug 0x00039a99 EmitMouseEvent + 132
7 MoniCheck.debug 0x00040c97 -[WindowView sendEvent:] + 474
8 com.apple.AppKit 0x93320813 -[NSApplication sendEvent:] + 5683
9 com.apple.AppKit 0x932b45bb -[NSApplication run] + 917
10 MoniCheck.debug 0x00003518 main + 580
11 MoniCheck.debug 0x00002879 _start + 208
12 MoniCheck.debug 0x000027a8 start + 40

Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x90c9f942 kevent + 10
1 libSystem.B.dylib 0x90ca005c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib 0x90c9f519 _dispatch_queue_invoke + 163
3 libSystem.B.dylib 0x90c9f2be _dispatch_worker_thread2 + 240
4 libSystem.B.dylib 0x90c9ed41 _pthread_wqthread + 390
5 libSystem.B.dylib 0x90c9eb86 start_wqthread + 30

Thread 2:
0 libSystem.B.dylib 0x90c9e9d2 __workq_kernreturn + 10
1 libSystem.B.dylib 0x90c9ef68 _pthread_wqthread + 941
2 libSystem.B.dylib 0x90c9eb86 start_wqthread + 30

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xc0000000 ebx: 0x00202c22 ecx: 0x00000000 edx: 0x00000000
edi: 0x93a83c60 esi: 0x031075a0 ebp: 0xbffff3c8 esp: 0xbffff350
ss: 0x0000001f efl: 0x00010206 eip: 0x00202d2f cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0xc0000000


ima747(Posted 2010) [#15]
If you don't need threading turn it off, the multithreaded garbage collector seems to have some problems (see http://www.blitzbasic.com/Community/posts.php?topic=91511 and the link there in for more examples of multithreaded GC freakout and other issues) so if you don't need it, I would say try to avoid it (turn it off by compiling for single thread only). If this problem is reproducable could you post a code example, as this might help find the issue since from the crash report it doesn't look like a whole lot is going on at the time of the crash...


MacSven(Posted 2010) [#16]
ima747:

It is no MultiThread build, it is really a problem with addgadgetitem!

Thanx.

I try to use cocoa extension to make a new GUI for my application.