PyMS v1.0.0 has just been released! Everyone should update for the many new features and bug fixes, which include:

• Online version checker
  
• Graphics and sound inserters/perviewers for PyICE
  
• GRP previews in PyDAT
  
• Increased graphics loading speeds (thanks to PIL, which is an optional extra download for the source users, but comes pre-packed for the EXE users)
  
• Saving/Loading from MPQ's and embedded MPQ's in PyDAT and PyAI
  

Edit: Fixed Hercanic, thanks (see below).

Post has been edited 2 time(s), last time on Dec 7 2008, 8:21 am by poiuy_qwert.

Sweet! Link updates in this thread (first post and update announcement post) are always helpful, though. =oP

http://www.broodwarai.com/index.php?page=pyms

O no! PyGRP has been corrupting my grps lately. I'm not exactly sure why, but I'll send you the .bmp next time you're online.

Are you sure the GRP's are corrupt? Try opening them in another editor. The reason im saying that is any error in the loading process (whether it be a corrupt GRP or a silly mistake by me in the code) will report a corrupt GRP. Anyway get the error report + grp/bmp + process you used to me asap and i'll look into it. Thanks!

Its the grp. pyGRP fails to reopen the grp and all other editors can't read it. SC crashes as well

My next project for PyMS:


If you didn't notice it is based heavily on HawTiles by FaRTy1billion (layout/labels).

Also, A_of_s_t, are you going to give me the errored stuff or not?

I can see that the controls are organized like in farty HawTiles

Yeah it is based heavily on HawtTiles by FaRTy (as stated in my original post about it), there have been some adjustments, but the core layout from HawtTiles works nice. Here are some updated screenshots:
Main window

Tile palettes:

I like it

Two things.

One: I opened PyTBL, did nothing, and when I tried to close it, I kept getting this message. So I had to end the process.

Exception in Tkinter callback
Traceback (most recent call last):
File "Tkinter.pyc", line 1403, in __call__
File "PyTBL.pyw", line 634, in exit
File "PyTBL.pyw", line 637, in destroy
TypeError: unbound method destroy() must be called with Toplevel instance as first argument (got NoneType instance instead)


Two: PyAI keeps closing on me. It doesn't say why.

The PyTBL problem has been fixed. And yeah that bug makes it impossible to close without ending its process An update will come out soon with the fix, thanks!

The problem with PyAI happens to some people, but I have no Idea how or why it happens since there is no error given or actually anything to show that there was a problem (except that it closes without the program even knowing it did). It seems to be a problem with the GUI toolkit that PyMS is built on top of (Tkinter), I'll see if maybe there is a newer version of it that will fix it, but currently there is nothing I can do Does it happen often? What are you usually doing when it happens? Is there anything consistent between the closes, like what you are doing, how long you have been running the program, switch between PyAI and StarCraft before it does it? I dunno if knowing that stuff will help but any info would be nice. Thanks again!

I think I recall having a similar problem if I closed the script editor, ran starcraft to test my updates, while keeping PYAI main window or even an aiscript.bin loaded. When I returned to the open PYAI, it would close IF/when I tried to open another script. The solution was to keep at least one script editor open if I tested in Starcraft and then returned to PYAI. ... All of this is a bit fuzzy right now, but I think those were the steps that caused PYAI to close. I'm sure poiuy documented what I described to him tho, and he can check his log notes as to this instance.

From fuzzy recollection tho:

--CAUSES PYAI to CLOSE--
>open an aiscript > open a script with the editor i.e. double-click > modify/save etc and then CLOSE script editor. > save (i.e. compile) and then run starcraft> exit starcraft > return to PYAI > Program will close if you try to open the script editor (i.e double-click on a script).

--AVOIDS PROBLEM--
Leave at least one script OPEN .. i.e the Editor open, then the program will not close when returning to it.

Actually that is a different problem, though they might be related. The one you are talking about baja is also caused by the GUI toolkit (maybe even the same problem with it), but it actually pops up an error dialog (windows error dialog not my own. PyMS once again doesn't know its closing/crashing).

I'm usually just typing my AI script. I don't ever go into SC in the middle of it.

Have you seen this? http://www.staredit.net/topic/5770/
Cheeze has some code in python that will split a map into its sections. Could that be useful for your program? Maybe add something that will extract a section so that the map doesn't need to be split beforehand like for using the trigger editor.

Pretty sweet, I didn't know about that. I might check it out, but I already have a chk editor started (only reason it hasn't been completed yet was my lack of an MPQ editor to get at the chk in the scm/scx), but that doesn't mean im making an editor (yet)

Edit: PyMS v1.1.0 has now been released! This includes the much needed PyTBL closing fix, and the new PyTILE, along with other new features/bug fixes. I recommend updating ASAP! One big change you should be aware of is the source version (what the Mac users and some Windows users use), now requires PIL to run. If your program isn't opening from the source version, that might be why. Check out the docs for a link to the download if you use the source version.

Post has been edited 2 time(s), last time on Jan 8 2009, 7:31 am by poiuy_qwert.

Im having a problem with MoveLocation in PyTRG. The documentation is incorrect as far as the order of the parameters. It should be Player, Unit, Location (Which one?), Location (Which one?). I dont know what order to put the locations in...

You'll notice that one of the parameters is named Location, and the other is named DestLocation. You are moving a location to a unit in the destination location.

Awesome! =oD Downloading now.

Using uflunstable causes PyICE to explode. (save and reload)
It also doesn't release the MPQ handle when it's not saving/loading files.