This is primarily a reminder for myself that I need to look into why the statusbar isn't repainting during a build. I have a feeling that the solution is to multi-thread the app, which would also give us the option of a Cancel button. I've been wanting to look into SwiXML for a while for maintenance reasons (every time I add a widget to the GUI, something breaks). I have a feeling that it would handle threading and synchronisation for us, but I mean to make sure of this before I go re-writing half of MIT again.
Statusbar Problems
Started by Orions_Stardom, Dec 07 2006 04:13 AM
4 replies to this topic
#1
Posted 07 December 2006 - 04:13 AM
#2
Posted 16 January 2007 - 04:52 PM
I'm stupid sometimes. I rewrote the GUI in SwiXML - didn't work. I fiddled round with threading - didn't work. I changed progress.paintImmediately(progress.getBounds()); to progress.revalidate(); - it worked.
Atleast I wanted to look at SwiXML anyway, although since I'm static linking, it more than doubled the size of the JAR...
Atleast I wanted to look at SwiXML anyway, although since I'm static linking, it more than doubled the size of the JAR...
#3
Posted 16 January 2007 - 05:02 PM
MultiInstall-20070117.jar is now with the new SwiXMLified GUI and a working progress bar.
#4
Posted 29 January 2007 - 06:50 PM
This is fixed without the new GUI in 5.0.1
#5
Posted 03 February 2007 - 05:46 PM
Ok, it was basically a coincidence that it was working on my system when I tested, and now it's stopped again. Damn. But I've looked into this a bit more, and I'm in the process of fixing it properly using javax.swing.SwingWorker, to /really/ run all of the create-the-clone stuff on a different thread to the update-the-gui stuff. This will also give us a Cancel button.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users











