How is somebody supposed to get MaxGUI to work?

BlitzMax Forums/MaxGUI Module/How is somebody supposed to get MaxGUI to work?

Reda Borchardt(Posted 2009) [#1]
Here is what I did,

1) Downloaded latest version of MaxGUI from my account
2) Copied the content to the mod folder
3) Rebuilt the documentation
3) Nothing compiles (cannot find maxgui.drivers)
4) Downladed MingW base + G++
5) Set the MingW Env. variable and modified the path
6) Selected Rebuild All with Quick Build and Threaded Off
7) Spent countless hours looking for a solution on the forums
7) Still cannot compile any of the MaxGUI samples

This is driving me nuts. I already bought this thing over one year ago and gave up because of the non-existant documentation and not being able to get MaxGUI to work.

Now that some useful tutorials have been written and thanks to Leadwerks I wanted to give it another shot and I still cannot get the bloody thing to work!

Am I completely stupid?


degac(Posted 2009) [#2]
1) Ok
2) ok
you should have something like

Blitzmax
+ Mod
-+ Brl.mod
-+Pub.mod
-+Maxgui.mod


3) you should have already installed Mingw to compile bmax module*
4) CTRL+D (Build Modules)
You shold see something like in the Output window in MaxIDE

Building modules
...



5) Rebuild documentation
6) choose an examples and try to compile it

Have you already tried to compile other modules (like something from Brucey)? Do you have problems with them too?


* this can be considered as step 0


Reda Borchardt(Posted 2009) [#3]
Thanks,

All the modules compile, but it fails to even attempt to compile the MaxGUI modules. I checked the permission on the Maxgui.mod folder and everything is fine.


degac(Posted 2009) [#4]

All the modules compile, but it fails to even attempt to compile the MaxGUI modules. I checked the permission on the Maxgui.mod folder and everything is fine.


What do you mean exactly?
What type of error?
What Windows version are you using?


Reda Borchardt(Posted 2009) [#5]
I am using Windows XP.

I am not getting any errors. It's as if MaxIDE doesn't see that I dropped the additional folder into the mod folder.


degac(Posted 2009) [#6]
Import MaxGui.Drivers
Strict 
Local window:TGadget
window=CreateWindow("My Window",40,40,320,240)
While True
	WaitEvent 
	Print CurrentEvent.ToString()
	Select EventID()
		Case EVENT_WINDOWCLOSE
			End
	End Select
Wend

This is the code example for CreateWindow.
Copy it and paste in a new window into MaxIDE, then run it.
What type of error you get?


Reda Borchardt(Posted 2009) [#7]
Can't find interface for module "maxgui.drivers"

BTW: Thanks for trying to help me out!!


degac(Posted 2009) [#8]

Can't find interface for module "maxgui.drivers"


Ok, are you sure that the Maxgui.mod folder is in the right place?
Please check your blitzmax folder and verify if it has a structure similar to what I post before.

I doubt even you have any sort of MaxGUI commands documents, dont'you?


Brucey(Posted 2009) [#9]
Hi reda :-)

Am I completely stupid?

Not at all.

It won't help much with degac's bit of non-clarity... so here's a quick summary as to where things should go :

The MaxGUI modules are in this folder structure :
    maxgui.mod
             - drivers.mod
             - maxgui.mod
 etc...

The maxgui.mod folder, you place into the following location :
  BlitzMax/mod/

So, if you have BlitzMax installed (on Windows) in C:\Program Files, a typical path might look like :
C:\Program Files\BlitzMax\mod\maxgui.mod\drivers.mod


That should allow the modules to be rebuilt.

You can test this on the command-line if you like, by running the following command from your BlitzMax\bin folder :
    bmk makemods -a maxgui


HTH


Reda Borchardt(Posted 2009) [#10]
OMG! I am stupid.
I copied the content of the maxgui.mod folder into the mod folder itself!

It works. Thank you very very much :)


Czar Flavius(Posted 2010) [#11]
OK now I know how to actually install and use this.


Wayne(Posted 2010) [#12]
This is good info for new buyers, thanks !


Czar Flavius(Posted 2010) [#13]
It's a pity it's not included. In any case, it's still not working properly. This is the code from the tutorial.


Null object error on line handle.context=FullPath.

I also cannot get TGadget to autocapitalise. This is so annoying. I HAVE WORK TO DO.


Czar Flavius(Posted 2010) [#14]
Pleeeeeeeeeeeeeease somebody tell me how to add things to a tree pleeeeeeeeeeeeeeeeaseeee.

I've tried AddTreeViewNode and .InsertItem and .InsertNode and nothing at all happens. In Insertxxxx what is index meant to be? How do I just add a node? It can be called anything. I just want to see a node!!!


Czar Flavius(Posted 2010) [#15]
http://www.blitzbasic.com/Community/posts.php?topic=78762#884114

>:(


VicToMeyeZR(Posted 2010) [#16]
Sounds like you didn't build the module after you got the files structure right.

Build modules again, then rebuild documentation.


jsp(Posted 2010) [#17]
Simple example:




skidracer(Posted 2010) [#18]
Reda, I would like to apologize for this shortfall. Brucey thanks for the instructions, I hope you don't mind but I have amended them to the email sent by the registration program to new MaxGUI users.

It now reads as follows:


Hi,

Thank you for buying the MaxGUI module for BlitzMax.

Here is your product key:

<%KEY%>

Please use this key to register your purchase at www.blitzbasic.com

Once you have registered your purchase, click on the Account tab and locate the MaxGui download link in the Product updates section of the website.

The MaxGUI modules are in this folder structure :

maxgui.mod
- drivers.mod
- maxgui.mod
...

Place the maxgui.mod folder into the following location :

BlitzMax/mod/

So, if you have BlitzMax installed (on Windows) in C:\Program Files, a typical path might look like :

C:\Program Files\BlitzMax\mod\maxgui.mod\drivers.mod



I'm thinking since Windows 7, BlitzMax installer now defaults to c:\BlitzMax, so maybe I should edit it again?


SebHoll(Posted 2010) [#19]
Place the maxgui.mod folder into the following location :

I would perhaps change this to...
Place the outer maxgui.mod folder into the following location:

...to avoid confusion.