October 11, 2012 
< | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | >
October 11, 2012 NOTICE: This channel is no longer actively logged.
[00:32:00] *** pVVEN has joined #nme[00:32:43] <pVVEN> Hello. :) Does anyone know of a class for writing log files? Capturing trace statements and exporting to a text file, something like that?[00:35:47] <singmajesty> You can override trace if you want[00:35:54] <singmajesty> Though depending on the target, it is already written to a log[00:37:38] <pVVEN> Oh, it does? Where does that file get saved to?[00:37:45] <singmajesty> Which target?[00:37:50] <pVVEN> Oh, Flash, sorry.[00:38:00] <singmajesty> Ah, for Flash it gets printed on-screen[00:38:03] <pVVEN> Flixel port, to be exact, but I figured NME might have its own thing.[00:38:10] <singmajesty> But there are some classes available for redirecting to the standard Flash trace output[00:38:39] <singmajesty> Flash doesn't have access to write to local files, but if you use the standard trace output there's a file on your system somewhere that it shows up[00:38:48] <singmajesty> If you built for the desktop, I think you can pipe the output[00:39:02] <singmajesty> ./MyCoolApp > output.log[00:39:10] <pVVEN> Oh, I thought Flash was auto-compiling for AIR[00:39:11] <singmajesty> or redirect, rather[00:39:18] <singmajesty> Nope, it's just Flash[00:39:25] <singmajesty> If you want AIR, use the target platform plus the "-air" flag[00:39:29] <singmajesty> like "nme test windows -air"[00:39:37] <singmajesty> But you'll need to run "nme setup air" first for that to work properly[00:39:50] <pVVEN> Ah, that's helpful, thanks. I know I'd run into that problem later. :P[00:40:10] <singmajesty> The Flixel port should work with native targets[00:40:34] <singmajesty> On the desktop it makes less of a difference, but on mobile the difference is big[00:41:40] * pVVEN makes a note of that.[00:42:04] <pVVEN> So for now I guess I'll have to make a textbox or something to copy from, huh.[00:42:20] <pVVEN> Flixel's debugger is great, except it has a stored character limit.[00:42:39] <pVVEN> Or at least a displayed character limit. Can only look back so far.[00:54:43] <pVVEN> Ah well, thanks for the help. :)[00:54:47] *** pVVEN has quit IRC[01:04:43] *** Jan_Flanders has quit IRC[01:32:54] *** singmajesty has quit IRC[01:51:15] *** Jan_Flanders has joined #nme[01:58:11] *** singmajesty has joined #nme[01:58:11] *** ChanServ sets mode: +o singmajesty[02:02:38] *** EzeQL_ has joined #nme[02:06:17] *** EzeQL_ has left #nme[02:06:20] *** EzeQL has quit IRC[02:12:33] *** PSvils has joined #nme[02:15:19] *** singmajesty has quit IRC[02:35:46] *** argylelabcoat has joined #nme[03:16:12] *** PSvils has quit IRC[03:17:35] *** filt3rek has quit IRC[04:00:34] *** justsee has joined #nme[04:06:53] *** Jan_Flanders has quit IRC[04:31:33] *** argylelabcoat has quit IRC[04:32:19] *** argylelabcoat has joined #nme[04:45:05] *** justsee has quit IRC[05:00:57] *** justsee has joined #nme[05:38:14] *** justinfront_ has quit IRC[06:15:23] *** argylelabcoat has quit IRC[06:19:26] *** justsee has quit IRC[06:20:02] *** justsee has joined #nme[06:20:07] *** justsee has joined #nme[07:45:39] *** justsee has quit IRC[07:52:59] *** justsee has joined #nme[08:55:50] *** ashes999 has quit IRC[09:30:11] *** PSvils has joined #nme[09:38:01] *** sspiff has joined #nme[09:42:12] *** justsee has quit IRC[09:45:21] *** Boorik has joined #nme[09:51:44] *** sspiff has quit IRC[09:52:54] *** sspiff has joined #nme[09:52:54] *** sspiff has joined #nme[10:22:56] *** filt3rek has joined #nme[10:56:29] *** tametick has joined #nme[11:06:15] *** Virtuall has quit IRC[11:21:57] *** Simn has joined #nme[11:32:02] *** justinfront_ has joined #nme[14:49:19] *** tametick has quit IRC[15:11:21] *** argylelabcoat has joined #nme[15:12:02] *** argylelabcoat has quit IRC[15:12:15] *** argylelabcoat has joined #nme[15:47:54] *** justsee has joined #nme[16:08:15] *** singmajesty has joined #nme[16:08:16] *** ChanServ sets mode: +o singmajesty[16:18:06] *** justsee has quit IRC[17:22:29] *** justinfront_ has quit IRC[17:25:52] *** justinfront_ has joined #nme[17:34:38] *** sspiff has quit IRC[18:32:31] *** justinfront_ has quit IRC[18:39:14] *** filt3rek|2 has joined #nme[18:42:05] *** filt3rek has quit IRC[19:09:37] *** PSvils has quit IRC[19:14:46] *** Boorik has quit IRC[19:18:51] *** empika has joined #nme[19:36:54] *** ashes999 has joined #nme[19:37:23] <ashes999> Why is DisplayObject.width/height a float?[19:37:35] <llamahunter> ask adobe[19:38:08] <ashes999> So NME just copies bad design decisions from Adobe?[19:38:18] <llamahunter> probably for backwards compatibility with as2, which did not have integer types.[19:39:37] <llamahunter> flash is still one of the output platforms for haxe/nme[19:40:34] <ashes999> Does that prevent nme.display.DisplayObject.width from being an Int? Couldn't NME provide an abstraction over this, instead of coupling it to the Flash API?[19:42:08] <llamahunter> probably… the legacy of haxe is flash, tho. I suspect it is an unfortunate historical artifact.[19:43:36] <ashes999> I guess nobody ever bothered "fixing" these little things that bug developers.[19:43:58] <ashes999> I should probably open a ticket or something, but it'll probably stay open forever :)[19:43:59] <llamahunter> does the float cause problems?[19:44:13] <ashes999> Well, as an API consumer, yes; it causes a lot of confusion[19:44:14] <llamahunter> or is your concern efficiency?[19:44:27] <ashes999> No, my concern is really just API design.[19:45:21] <llamahunter> there's the potential that, with 3D output, floating point positions, etc, becomes more important.[19:46:18] * ashes999 shrugs[19:46:43] <ashes999> it might be if you're implementing something like velocity or scale-rate, having a float allows you, on computers with a very fast FPS, to actually scale/move properly -- I've seen that issue before[19:47:03] <ashes999> if you have an int, you can get something like "this.x += velocity * delta" where velocity*delta < 1[19:47:34] <ashes999> On the other hand -- especially when I'm building my own API on top of Haxe/NME -- it seems very odd to have width/height/x/y as floats instead of ints. Because they are pixels.[19:47:55] <llamahunter> I agree it seems awkward, but dunno if anything can be done about it at this point. you'd have to ask the haxe & nme maintainers.[19:48:14] <Simn> Flash had subpixel accuracy for years now.[19:51:56] <Simn> But I'm sure tweening would be a lot of fun if dimensions where strictly Int-based. ;)[19:52:02] <Simn> *were[19:53:29] <ashes999> I love how you ask in #haxe and they say "oh it's a bug"[19:54:10] <ashes999> do Hugh and Joshua actually show up in either of these channels?[19:55:02] <Simn> Yes Joshua is right here, but I'm not sure if you actually want help or just look for a place to rant. ;)[19:56:19] *** ashes999|home has joined #nme[19:57:52] *** ashes999|again has joined #nme[19:58:19] <Simn> Oh dear, he brought reinforcements.[20:00:09] *** ashes999 has quit IRC[20:01:17] *** ashes999|home has quit IRC[20:01:48] *** ashes999|again is now known as ashes999[20:27:48] *** tametick has joined #nme[20:55:47] <ousado> heh, if you declare a thing that is an Int as Float or the other way 'round I don't really remember, and things therefore blow up, it's most certainly a bug ;)[20:58:10] *** benth has quit IRC[21:09:52] *** justinfront_ has joined #nme[21:44:07] <ousado> .. just to clarify, your whining about something being a Float coincides with an actual bug/wrong declaration in the externs, it's been a few weeks since that came up[21:50:16] <Simn> What bug? DisplayObject dimensions have always been Floats.[21:53:53] *** ue has joined #nme[22:04:22] <ashes999> don't you guys have anything better to do than sit and cause problems for people who are new to Haxe and NME?[22:04:40] <ashes999> it's disgusting how closed the Haxe community is. It's like a private insider-nerds-only club.[22:04:47] *** ashes999 has left #nme[22:05:39] <Simn> We must be pretty popular when people start nerdraging about us...[22:12:52] <ousado> Simn: there was a bug, they were declared wrongly, leading to some error, a few weeks ago.[22:13:03] <ousado> Asmageddon encountered it[22:13:30] <ousado> mismatch between what came from hxcpp and the extern declaration[22:17:05] <Simn> But ashes was whining about the dimensions being floats in general.[22:17:37] <ousado> yes, I misinterpreted his question as something being worth answering[22:17:44] <ousado> that was yesterday[22:18:17] <ousado> he referred to that as 'I love how you ask in #haxe and they say "oh it's a bug"'[22:18:54] *** tametick has quit IRC[22:21:49] <ousado> .. so after accusing #haxe people of keeping harassing him about how haxe is not nme, I thought I'd clarify at least that one[22:21:52] <Simn> Ah well, he was entertaining for a while.[22:22:13] <ousado> *after his[22:32:00] *** argylelabcoat has quit IRC[23:05:17] *** Virtuall has joined #nme[23:14:41] *** Simn has quit IRC[23:22:33] *** Virtuall has quit IRC[23:53:06] <singmajesty> Hmm, sorry I wasn't here.[23:53:15] *** benth has joined #nme[23:53:20] <singmajesty> DisplayObject width and height is a float, because it obviously can be an uneven size.[23:53:34] <singmajesty> :/[23:55:07] <llamahunter> But, most of the time, it's probably integral, no? I think that was the comment. When displaying to bitmap output devices, using floats for position and size seems not efficient. I understand this is probably just flash <8 legacy.