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 »
451
Proposals / Re: Action functions plugin writing
« on: March 01, 2011, 10:49:05 pm »
Why is argument_relative not passed as a function parameter from actions?
452
Proposals / Re: Function approval process
« on: March 01, 2011, 05:45:17 pm »
Well I'm happy with it and Ism seems so. I guess we should get Josh's opinion. EDIT: Quote Josh "I like the Wiki idea, but we need the attention the forums draw. Perhaps linking to a Wiki."
What about functions that have already been implemented? A list of those should also be populated on the wiki also then people can just document them whenever.
What about functions that have already been implemented? A list of those should also be populated on the wiki also then people can just document them whenever.
453
Proposals / Re: Function approval process
« on: March 01, 2011, 05:06:46 pm »
OK I'm starting to warm more to the idea of the wiki. Are you going to start it off? Then we can see how it goes.
454
Proposals / Re: Function approval process
« on: March 01, 2011, 02:36:58 pm »
I suppose a forum post would work as a reminder, but then like moderation it will take some commitment from someone to actually do it. What's more importantly needed here as well as the process being changed is someone committed to keeping things organised and moving forwards.
455
Function Peer Review / Re: move_wrap
« on: March 01, 2011, 01:32:01 pm »I. Did. This. One. FFS.a) That's not more efficient, it's different. And by being different it does not behave how the function behaves in GM. I don't just stick shit into code randomly
And more efficiently.Code: (Something that looks like C++ and is easily portable) [Select]//int move_wrap(double hor,double vert,double margin)
int move_wrap(double hor,double vert,double margin) {
//not sure whether two IFs are faster than one big calculation in a single IF
if (hor) {
if (X < -margin || X > room_width+margin) {
X = -(X-room_width);
}
}
if (vert) {
if (Y < -margin || Y > room_height+margin) {
Y = -(Y-room_height);
}
}
return (int)0;
}
Since Josh fails to remember or care (<_<), I post this code.
b) It's not written properly. Wtf are X and Y going to do?
456
Proposals / Re: Function approval process
« on: February 28, 2011, 09:14:35 pm »
Ok I see your point, if it's left till later it will probably be left for a long time. What about if there is an extra step in the forum procedure? Where after testing is done the function must be documented on the wiki before it is committed. People will be more likely to document things then if there is the benefit of having it committed afterwards.
457
Proposals / Re: Function approval process
« on: February 28, 2011, 08:35:55 pm »
Hmm the wiki is probably better for the long term, I guess that is where things could become organised and standardised so it is unneeded on the forum. But the main reason for suggesting this is to try and drive progress, which the forum is best for right now. The wiki can all be written later.
Also with the wiki what about user functions that aren't going to be committed, where to they fit into things?
Also with the wiki what about user functions that aren't going to be committed, where to they fit into things?
458
Function Peer Review / move_wrap
« on: February 28, 2011, 05:47:52 am »Code: (C++) [Select]
void move_wrap(bool hor, bool vert, double margin)
{
enigma::object_planar* const inst = ((enigma::object_planar*)enigma::instance_event_iterator->inst);
if (hor)
{
const double wdis = room_width + margin*2;
if (inst->x < -margin)
{
inst->x += wdis*ceil(((-margin) - inst->x)/wdis);
}
if (inst->x > room_width + margin)
{
inst->x -= wdis*ceil((inst->x - (room_width + margin))/wdis);
}
}
if (vert)
{
const double hdis = room_height + margin*2;
if (inst->y < -margin)
{
inst->y += hdis*ceil(((-margin) - inst->y)/hdis);
}
if (inst->y > room_height + margin)
{
inst->y -= hdis*ceil((inst->y - (room_height + margin))/hdis);
}
}
}
459
Proposals / room_speed
« on: February 28, 2011, 03:03:22 am »
What's with the room_speed? Setting to 30, it certainly looks to be running a lot more than 30 steps every second.
Tracker Reference:
http://enigma-dev.org/tracker/ticket.php?id=86
Tracker Reference:
http://enigma-dev.org/tracker/ticket.php?id=86
460
Proposals / Function approval process
« on: February 28, 2011, 02:01:49 am »
I think the function approval process could use some work. It's not exactly organised at the moment and not much seems to happen. It should be structured in a way so people know what is going on and things are kept moving.
I propose several sub-forums for the function approval system:
- Review
- Testing
- Committed
- User
- Rejected
All functions are first posted in the Review sub-forum. Here they are discussed and optimised fully, when they appear to be written properly they are then moved to the Testing sub-forum. Here anyone can test the function and mark as working correctly. Then they should finally be moved to either the Committed or User sub-forum, depending on whether it is a function that should be committed or just a user-made function that can be used by people. Before moving to the Committed forum functions should also be committed to the SVN. The Rejected sub-forum is obviously for any functions that are not considered useful and thus sent out of the approval process.
By changing to this system hopefully it will drive more progress forward, it will then also leave a nice list of committed and user functions which people can easily browse.
I'm not even sure how this board is moderated, but if the proposal does come to light it might be helpful to have some local mods in the forum to help. And just an extra suggestion that the list of missing and finished GM functions should be pinned somewhere in the forum.
I propose several sub-forums for the function approval system:
- Review
- Testing
- Committed
- User
- Rejected
All functions are first posted in the Review sub-forum. Here they are discussed and optimised fully, when they appear to be written properly they are then moved to the Testing sub-forum. Here anyone can test the function and mark as working correctly. Then they should finally be moved to either the Committed or User sub-forum, depending on whether it is a function that should be committed or just a user-made function that can be used by people. Before moving to the Committed forum functions should also be committed to the SVN. The Rejected sub-forum is obviously for any functions that are not considered useful and thus sent out of the approval process.
By changing to this system hopefully it will drive more progress forward, it will then also leave a nice list of committed and user functions which people can easily browse.
I'm not even sure how this board is moderated, but if the proposal does come to light it might be helpful to have some local mods in the forum to help. And just an extra suggestion that the list of missing and finished GM functions should be pinned somewhere in the forum.
461
Function Peer Review / Re: action_move_to
« on: February 28, 2011, 12:03:54 am »
I meant when using action_ functions. In gml the relative argument doesn't seem to be used..
462
Function Peer Review / action_move_to
« on: February 27, 2011, 08:17:43 pm »Code: (C++) [Select]
inline void action_move_to(double x, double y)
{
enigma::object_planar* const inst = ((enigma::object_planar*)enigma::instance_event_iterator->inst);
if (argument_relative)
{
inst->x += x;
inst->y += y;
}
else
{
inst->x = x;
inst->y = y;
}
}
How the fuck does relative work? It isn't specified as an argument in gml....
463
Proposals / Re: Script Editor Features
« on: February 19, 2011, 11:48:48 pm »
1) Options for all features, very important for me. Like being able to turn off line numbering, any highlighting features added, change highlighting colours etc.
2) Automatic syntax checking when closing the editor, warns user upon syntax error.
3) Bracket highlight colouring feature. For example upon hotkey it would look like this:
{
text, text, text
{
text, text, text
text
{
text, text, text, text
}
}
text
text
{
text
}
}
Also an alternative for brackets and strings. This is perhaps the best way to visually see things in my opinion.
4) Smart code snippet feature. For example you can put whatever common code snippet pieces in a text file you wish, like:
for (i = 0; i < $; i += 1)
{
$
}
then upon a hotkey it insert the code snippet into the editor, like:
for (i = 0; i < ; i += 1)
{
}
and moves the cursor automatically to the first $ sign for typing, then upon another hotkey it moves to the second $ sign then to the end of the snippet piece. Not sure how it's best to choose from different code snippets from the hotkey, ideally upon the hotkey press the user should be able to see the different code snippet choices (without it getting in the way) then can press corresponding key to insert a snippet.
5) Add a help menu so a user can see all the script editor hotkeys easily.
6) Feature to indent/unindent selected lines a certain amount of space
7) CTRL selecting, allowing to select multiple text at once.
8) Math calculations. For example you highlight 2 + 3 press a hotkey it changes it to 5, or highlight 34*5 it changes it to 170.
I'll probably think of more things. Feel free to shoot them down, I don't think any suggestions through
2) Automatic syntax checking when closing the editor, warns user upon syntax error.
3) Bracket highlight colouring feature. For example upon hotkey it would look like this:
{
text, text, text
{
text, text, text
text
{
text, text, text, text
}
}
text
text
{
text
}
}
Also an alternative for brackets and strings. This is perhaps the best way to visually see things in my opinion.
4) Smart code snippet feature. For example you can put whatever common code snippet pieces in a text file you wish, like:
for (i = 0; i < $; i += 1)
{
$
}
then upon a hotkey it insert the code snippet into the editor, like:
for (i = 0; i < ; i += 1)
{
}
and moves the cursor automatically to the first $ sign for typing, then upon another hotkey it moves to the second $ sign then to the end of the snippet piece. Not sure how it's best to choose from different code snippets from the hotkey, ideally upon the hotkey press the user should be able to see the different code snippet choices (without it getting in the way) then can press corresponding key to insert a snippet.
5) Add a help menu so a user can see all the script editor hotkeys easily.
6) Feature to indent/unindent selected lines a certain amount of space
7) CTRL selecting, allowing to select multiple text at once.
8) Math calculations. For example you highlight 2 + 3 press a hotkey it changes it to 5, or highlight 34*5 it changes it to 170.
I'll probably think of more things. Feel free to shoot them down, I don't think any suggestions through
464
Proposals / Script Editor Features
« on: February 19, 2011, 11:16:46 pm »
While Josh and Ism are currently working on the script editor post any features or suggestions for it here.
Please number your suggestions so they are easier to reply to.
If you come up with more suggestions after you have already posted, start a new post and continue your numbering where you left off. This way, suggestions can be identified by Username#SuggestionNumber.
Please number your suggestions so they are easier to reply to.
If you come up with more suggestions after you have already posted, start a new post and continue your numbering where you left off. This way, suggestions can be identified by Username#SuggestionNumber.
465
General ENIGMA / Re: Hey
« on: February 13, 2011, 10:07:57 pm »
Wow a new face, well it's not new I recognise you from the GMC
Get on the IRC chat
Get on the IRC chat