This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: « 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 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 »
1606
Proposals / Re: Preprocessor Directives (The compile-time "if")
« on: November 06, 2010, 02:00:43 pm »
"__preproc__ int x = 2;"
"Also, mandatory is official #pragma once support"
wat is this i dont even
"Also, mandatory is official #pragma once support"
wat is this i dont even
1607
Proposals / Re: Thoughts on forum registration...
« on: November 06, 2010, 01:20:15 pm »
That's just annoying, serp. XD
1608
Proposals / Re: Preprocessor Directives (The compile-time "if")
« on: November 06, 2010, 10:42:18 am »
I see what you mean, Rusky. For a little bit I was thinking about doing something like that (C takes a lot of heat over the issues rising from copy-pasted macros, of course), but I don't think I should. The only reason I'm keeping any sort of macros is because of ENIGMA's C heritage. If it wasn't for that, they'd be expression based if they were in at all, but my reason for wanting preprocessors at all at this point isn't for macros. My number one concern is the #if directive. The rest are just kind of there. The reason I want #if is for altering behavior from platform to platform. I was discussing with marbs the other day the implications of ENIGMA compiling for iPhone, and he mentioned motion detecting devices.
Originally, I intended to offer controller_get_angle_x/y/z() and controller_get_shaken(). On Windows, they'd all return zero unless an applicable device was connected. On Wii, they'd all have an accurate return. On iPhone, _angle _x and _y would work, as well as _shaken (same for android). Issue is, what if that isn't enough? What if having a shake is a critical part of the game, and they would have to work around it with multiple lines of code (likely to test for a key combo instead)?
I like a number of features for Lisp's macros, but my focus is really more on preprocessors right now. Maybe we can pile on a new macro system as well, later. But for now I'm more concerned about being able to say
[[If Target_Device == eDev_iPhone]]
if (controller_get_shaken())
earthquake();
[[else]]
if (keyboard_check(vk_control) and keyboard_check_pressed(ord("E")))
earthquake();
[[fi]]
Granted, that's not a very good example, since a simple "or" could technically have sufficed with little overhead. But it conveys the basic idea.
Say we want our mobile game to always be oriented correctly, and which direction has the high resolution doesn't really matter.
Persistent Controller Step Event:
Originally, I intended to offer controller_get_angle_x/y/z() and controller_get_shaken(). On Windows, they'd all return zero unless an applicable device was connected. On Wii, they'd all have an accurate return. On iPhone, _angle _x and _y would work, as well as _shaken (same for android). Issue is, what if that isn't enough? What if having a shake is a critical part of the game, and they would have to work around it with multiple lines of code (likely to test for a key combo instead)?
I like a number of features for Lisp's macros, but my focus is really more on preprocessors right now. Maybe we can pile on a new macro system as well, later. But for now I'm more concerned about being able to say
[[If Target_Device == eDev_iPhone]]
if (controller_get_shaken())
earthquake();
[[else]]
if (keyboard_check(vk_control) and keyboard_check_pressed(ord("E")))
earthquake();
[[fi]]
Granted, that's not a very good example, since a simple "or" could technically have sufficed with little overhead. But it conveys the basic idea.
Say we want our mobile game to always be oriented correctly, and which direction has the high resolution doesn't really matter.
Persistent Controller Step Event:
Code: (EDL) [Select]
[[if Target_Device == eDev_iPhone or Target_Device == eDev_Android]]
int az = controller_get_angle_z();
if (az > 45 and az < 135 or az > 225 and az < 315)
view_wview[0] = display_get_width(),
view_wview[0] = display_get_height%
1609
Announcements / Re: Long enough without an update
« on: November 06, 2010, 10:18:55 am »
I need to offer preprocessors in ENIGMA. But I'm NOT using C's.
I'll make a post under proposals.
Done. http://enigma-dev.org/forums/index.php?topic=676
I'll make a post under proposals.
Done. http://enigma-dev.org/forums/index.php?topic=676
1610
Off-Topic / Re: Wayland (aka DIE X11 DIE)
« on: November 05, 2010, 09:39:54 pm »
I'm usually in favor of preserving, though my public track record doesn't suggest it. (In all honesty, there's no hope for GM, and there was no hope for even the better aspects of R3's instance system and parser sync.)
X has been, recently, much better about not crashing and dying all the damn time. The sheer motivation they must have attained in seeing that the project would otherwise be replaced probably got them going again on the errors. Look at Pidgin. Empathy replaces Pidgin; next thing you know, pidgin has voice and video support.
I haven't seen X's code, so I can't speak for whether or not it should be scrapped. I trust a group of GNUs to make the right choice.
But if they totally fuck up the API and still don't offer widgets natively, I'm going to flip shit.
(Nah, I'm actually pretty much over it at this point.)
X has been, recently, much better about not crashing and dying all the damn time. The sheer motivation they must have attained in seeing that the project would otherwise be replaced probably got them going again on the errors. Look at Pidgin. Empathy replaces Pidgin; next thing you know, pidgin has voice and video support.
I haven't seen X's code, so I can't speak for whether or not it should be scrapped. I trust a group of GNUs to make the right choice.
But if they totally fuck up the API and still don't offer widgets natively, I'm going to flip shit.
(Nah, I'm actually pretty much over it at this point.)
1611
Proposals / Re: Thoughts on forum registration...
« on: November 05, 2010, 09:27:44 pm »
I kind of like what the second question is getting at. Basically, I'm going for things the typical ENIGMA user would know. (Or should go fucking learn before asking about it here <_<).
1612
Announcements / Re: Long enough without an update
« on: November 05, 2010, 10:24:09 am »
I call that a fluke.
...
...
1613
Off-Topic / Re: Wayland (aka DIE X11 DIE)
« on: November 05, 2010, 09:36:53 am »
That explains why X.org finally fixed that Java bug. Or someone did.
People tend to work better under threat of discontinuation.
People tend to work better under threat of discontinuation.
1614
Announcements / Re: Long enough without an update
« on: November 05, 2010, 09:17:57 am »
I'm confident in saying that aside from iPhone support, nothing will ever work in Mac that doesn't work better in Linux.
And yeah, with() is platform-independent entirely.
But I'm not gonna skewer anyone over it.
And yeah, with() is platform-independent entirely.
But I'm not gonna skewer anyone over it.
1616
Off-Topic / Re: i'm like srsly guys
« on: November 04, 2010, 09:33:03 pm »
what is this i dont even
1617
Announcements / Re: Long enough without an update
« on: November 04, 2010, 09:32:09 pm »
Win32. The menu function was in fact ported from Win32 to GTK. I even used a couple enum{} wrappers so the code is nearly identical. Getting the Win32 version to tab-switch and resize dynamically is going to take much more work. The only reason I used GTK is because it's as native as you can get on GNOME.
1618
Off-Topic / Re: Does the tracker need severity?
« on: November 04, 2010, 12:21:31 pm »
I was going to let them set it, but make it really easy for an admin to edit. I told a2h from square one that everyone will either neglect to choose a rating or give their own urgent status. At this juncture we see less people thinking their problem is urgent, and more who either don't set the severity past "suggestion" or don't realize that their issue is in fact much more severe than they can actually tell.
1619
Proposals / Re: Thoughts on forum registration...
« on: November 04, 2010, 12:19:27 pm »
Yes, without a pointed question about ENIGMA, I suppose so. (SMF's verification questions are disdainfully featureless; I had to program in the patch for multiple answers myself).
Feel free to recommend some and their appropriate regexes. (No / at start and end; that's automatic.)
Feel free to recommend some and their appropriate regexes. (No / at start and end; that's automatic.)
1620
Function Peer Review / Re: action_move
« on: November 04, 2010, 12:17:03 pm »
- Like I said, shouldn't matter.
- Until choose is implemented, the macro isn't possible.
- Well, now you know. Have you implemented it?
-
- Until choose is implemented, the macro isn't possible.
- Well, now you know. Have you implemented it?
-
Pages: « 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 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 »