[CC 1.3 / 1.4] Load Screen / Bar API — The first REALTIME load screen — Use your logo as progress! Now you can have multiple progress bars!
Started by theoriginalbit, Jan 11 2013 03:51 PM
api utility
37 replies to this topic
#21
Posted 13 January 2013 - 01:08 PM
Ah, just a bar, yeah that makes more sense
#23
Posted 13 January 2013 - 01:16 PM
999 o_O, i highly doubt anyone will use that many lol, or even able to.
Even if you make the block 1x1, there's only a max of 969 blocks.
Adv PC's are 19x51?
19x51 = 969 so yeah...
Even if you make the block 1x1, there's only a max of 969 blocks.
Adv PC's are 19x51?
19x51 = 969 so yeah...
#24
Posted 13 January 2013 - 01:20 PM
remiX, on 13 January 2013 - 01:16 PM, said:
999 o_O, i highly doubt anyone will use that many lol, or even able to.
Even if you make the block 1x1, there's only a max of 969 blocks.
Adv PC's are 19x51?
19x51 = 969 so yeah...
Even if you make the block 1x1, there's only a max of 969 blocks.
Adv PC's are 19x51?
19x51 = 969 so yeah...
#25
Posted 13 January 2013 - 01:23 PM
Oh yeah, right. Do they get destroyed once all the 'steps' are done? Can't remember what was in the api
#26
Posted 13 January 2013 - 01:30 PM
remiX, on 13 January 2013 - 01:23 PM, said:
Oh yeah, right. Do they get destroyed once all the 'steps' are done? Can't remember what was in the api 
Well the released one was just a standard API so there was no destroy code... this one however since they are all objects will have dealloc code yes... still deciding if it should be auto dealloc or manual though... I would make it manual if I added a reset() method... thoughts?
#27
Posted 13 January 2013 - 01:47 PM
Hmm, both?
Add another argument in the calling of the bars for a 'timeout' if you can. Then after that amount of seconds, the object get's destroyed. Or can destroy it with load.destroy()
Add another argument in the calling of the bars for a 'timeout' if you can. Then after that amount of seconds, the object get's destroyed. Or can destroy it with load.destroy()
#28
Posted 13 January 2013 - 01:55 PM
hmmm ok I'll do that... we shall see how well the timeout thing works...
#29
Posted 13 January 2013 - 02:46 PM
Just thinking about it then, and realised that a timer to destroy won't work... id have to pull all events and check the event then, id prefer it stay only pulling its own events...
#30
Posted 13 January 2013 - 03:35 PM
wouldn't it be cool if you like changed os.pullEvent or something so that it stores the events, thus you can save to a file how many events take to load the program and for the next startup just check percentages with the 2 numbers.
Though, were cool API!
Though, were cool API!
#31
Posted 13 January 2013 - 03:38 PM
Doyle3694, on 13 January 2013 - 03:35 PM, said:
wouldn't it be cool if you like changed os.pullEvent or something so that it stores the events, thus you can save to a file how many events take to load the program and for the next startup just check percentages with the 2 numbers.
Though, were cool API!
Though, were cool API!
Thank you
#32
Posted 14 January 2013 - 12:22 AM
UPDATE v2.0!
Full rewrite of API, load screen / bars are now objects... 2 new modes...
See OP for more details...
Full rewrite of API, load screen / bars are now objects... 2 new modes...
See OP for more details...
#33
Posted 14 January 2013 - 02:03 AM
Edited OP with 'Examples of Usage' code... Also new version with a few bugs squished...
#34
Posted 14 January 2013 - 02:43 AM
Nice
#36
#37
#38
Posted 25 January 2013 - 12:49 AM
Locked by request.
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users


This topic is locked









