37 replies to this topic

[remiX]

Ah, just a bar, yeah that makes more sense

[theoriginalbit]

remiX, on 13 January 2013 - 01:08 PM, said:

Ah, just a bar, yeah that makes more sense

Yeh...

just added this error message

if #usedIds == 999 then error( "Maximum load bars reached, you have used 999, how?! Tell me on the forum post! Better yet, SHOW ME!" ) end

[remiX]

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...

[theoriginalbit]

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...

Its objects, and it keeps track of the objects, they don't all have to be displaying at once, just created...

[remiX]

Oh yeah, right. Do they get destroyed once all the 'steps' are done? Can't remember what was in the api

[theoriginalbit]

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?

[remiX]

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()

[theoriginalbit]

hmmm ok I'll do that... we shall see how well the timeout thing works...

[theoriginalbit]

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...

[Doyle3694]

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!

[theoriginalbit]

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!

It would be quite cool to do, but I think the implementation of it would be quite difficult, since on first run it would have no idea of event counts... but thank for the suggestion

Thank you

[theoriginalbit]

UPDATE v2.0!


Full rewrite of API, load screen / bars are now objects... 2 new modes...

See OP for more details...

[theoriginalbit]

Edited OP with 'Examples of Usage' code... Also new version with a few bugs squished...

[remiX]

Nice

[theoriginalbit]

remiX, on 14 January 2013 - 02:43 AM, said:

Nice

Haha thanx... biggest update I've ever done... hardest update I've ever done... felt like I wrote so much more than ~500 lines of code!

[remiX]

TheOriginalBIT, on 14 January 2013 - 02:44 AM, said:

remiX, on 14 January 2013 - 02:43 AM, said:

Nice

Haha thanx... biggest update I've ever done... hardest update I've ever done... felt like I wrote so much more than ~500 lines of code!

Like a boss

There's not much you can add now, is there? xD

[theoriginalbit]

remiX, on 14 January 2013 - 04:18 AM, said:

TheOriginalBIT, on 14 January 2013 - 02:44 AM, said:

remiX, on 14 January 2013 - 02:43 AM, said:

Nice

Haha thanx... biggest update I've ever done... hardest update I've ever done... felt like I wrote so much more than ~500 lines of code!

Like a boss

There's not much you can add now, is there? xD

Nah I have a feeling it just might be a few little things... like the Apple OS 9 style, and the iPhone style... other than that, I don't think there is much left...

[AfterLifeLochie]

Locked by request.