Epic metal from Cincinnati
After years of silence and slumber, something stirs. Darkness looms over worlds untold as the fetus of a savage new god kicks. Pantheons crumble and the faithful weep as the cosmos gives birth to a new dark conqueror.
Four brothers, black of armor and void of soul, roar in adoration and corrupt praise. The Fallen rises, accompanied by hymns that drone like sanity's funeral dirge...
Siegelord captures the essence of this morbid tale, presenting it to you with musicianship both dark and powerful. Hope shall be forfeit when such soundscapes of war echo through forgotten lands... and when the last cry for battle has left our lungs you shall know the Fallen has ascended.
Ulfr: Vocals/Bass
Sieven: Drums
Therod: Guitar
After years of silence and slumber, something stirs. Darkness looms over worlds untold as the fetus of a savage new god kicks. Pantheons crumble and the faithful weep as the cosmos gives birth to a new dark conqueror.
Four brothers, black of armor and void of soul, roar in adoration and corrupt praise. The Fallen rises, accompanied by hymns that drone like sanity's funeral dirge...
Siegelord captures the essence of this morbid tale, presenting it to you with musicianship both dark and powerful. Hope shall be forfeit when such soundscapes of war echo through forgotten lands... and when the last cry for battle has left our lungs you shall know the Fallen has ascended.
Ulfr: Vocals/Bass
Sieven: Drums
Therod: Guitar
Attachments:On Thu, Mar 10, 2016 at 7:58 PM, Elias Pschernig wrote: I'm confused, you say this patch grabs mouse-movement events in XInput2, then you say input + windows + mouse are handled by the legacy API - so which one is it for mouse? Or is movement handled by XInput2 and buttons with legacy? Would there be any advantage in handling more events with XInput2?With this patch, only Mouse movement will be handled by Xinput2 ifavailable.the remaining mouse events: mouse buttons, and wheel events, etc. Are allstill handled by the legacy API.window events (enter, leave, focus, etc.), other inputdevices+events(joystick, etc). Are all still handled by the legacy API.According to Xorg docs:Xinput 2.2 adds multitouch support. Clients can, for example, nowdistinguish between a one-finger slide and a two-finger swipe.
Copyright Office Section 115 Electronic - Notice of Intention to Obtain a Compulsory License for Making and Distributing Phonorecords 201.18(d)(1).
Multitouchsupport adds on to enhancements in previous versions. These included inputdevice properties to pass additional metadata and configuration informationbetween devices and clients; also the MultiPointer X (MPX) feature. MPXallows for multiple X users to share a single X desktop. On Thu, Mar 10, 2016 at 4:26 PM, Phelius wrote: Attached is a patch that enables Xinput2 API for processing mouse-movement.Thanks! No new functionality is implemented. Notes: -I refactored/moved the x11 touch input setup stuff since it also gets used for the mouse -touchpad events were implemented in Xinput 2.1, but touchscreen events are in ver 2.2 I simply made 2.2 the minimum requirement. Attachments:Attached is a patch that enables Xinput2 API for processing mouse-movement.No new functionality is implemented.Notes:-I refactored/moved the x11 touch input setup stuff since it also gets usedfor the mouse-touchpad events were implemented in Xinput 2.1, but touchscreen events arein ver 2.2I simply made 2.2 the minimum requirement.
On Sat, 15 Aug 2015 13:59:46 -0600, Thomas Fjellstrom wrote: On Fri 14 Aug 2015 10:26:36 PM SiegeLord wrote: While posting to it a few times, I've noticed that things went into the moderation queue. I'm not sure what alleg-developers@. Is doing right now, but I was under the impression that it was not moderated. Could we turn that off for gna as well (if sourceforge is moderated, then nevermind, I must have never noticed it).
Just concerned about the workload of whitelisting people by the busy moderator(s). Afaik it is/was moderated. I thought elias disabled that at some point, but i could be wrong. For a long time noone was even moderating it.The gna list was on the default setting so posts by non-members would beheld in a queue. I had to approve SL's first post but that was it.I have opened the list to posts by non-members.If spam turns out to be an issue, we can rethink it.As for the AD list on SourceForge, consider it closed.Actually it's just hidden from view.
Posts like this should still gothrough. There may be something in the mailman admin area, but I don'thave the password to it.Peter. On Sat, 15 Aug 2015 20:31:32 -0400, Elias Pschernig wrote: On Fri, Aug 14, 2015 at 11:06 PM, Peter Wang wrote: HiWill anything bad happen if I delete the Donate link on the SourceForge page?
I don't want to leave it there when we're moving away. It should be removed.Done. I'd still kinda like (someone) to redo the whole website - I feel it's time for a new layout plus some stuff should be migrated to the wiki, like the DIGMID, Logos or Humor pages - but I guess that's not really important right now.Yeah, most of the web site is just there because it was there in thepast.Peter. Is only not moderated forsubscribers, all other mails go into a moderation queue that is neverreviewed I think. I hope it will be different for the new list.Best,TobiasAm um 07:26 schrieb SiegeLord: While posting to it a few times, I've noticed that things went into the moderation queue. I'm not sure what alleg-developers@. Is doing right now, but I was under the impression that it was not moderated.
Could we turn that off for gna as well (if sourceforge is moderated, then nevermind, I must have never noticed it). Just concerned about the workload of whitelisting people by the busy moderator(s).SL On 06:33 PM, Peter Wang wrote: Hi, Allegro has been accepted as a project on Gna! I have created a new mailing list. Please subscribe if you are interested. Subscriptions from the old mailing list will NOT be automatically transferred to the new list. I intend to shut down the old list in about one week, then transfer the archives. In the mean time, please cross-post messages to both lists.
See you there. Peter P.S. Could a couple of interested parties sign up and request to join the Gna project (or however it is done) so we have multiple admins. Thanks. While posting to it a few times, I've noticed that things went into themoderation queue. I'm not sure whatalleg-developers@.
Is doing right now, but I wasunder the impression that it was not moderated. Could we turn that offfor gna as well (if sourceforge is moderated, then nevermind, I musthave never noticed it). Just concerned about the workload ofwhitelisting people by the busy moderator(s).-SLOn 06:33 PM, Peter Wang wrote: Hi, Allegro has been accepted as a project on Gna! I have created a new mailing list. Please subscribe if you are interested. Subscriptions from the old mailing list will NOT be automatically transferred to the new list.
I intend to shut down the old list in about one week, then transfer the archives. In the mean time, please cross-post messages to both lists. See you there. Peter P.S. Could a couple of interested parties sign up and request to join the Gna project (or however it is done) so we have multiple admins. Thanks. That's great!
Yes, indeed there's quite a few files of. Historicalinterest still on SourceForge.
I think some of them would appropriatelybe put inside the website perhaps.-SLOn 07:51 PM, Peter Wang wrote: Hi, I uploaded our files to Gna: It would have been a good chance to reorganise things a bit, but I didn't. Feel free to, if you like. Some documentation-related files are still only on SourceForge. I'm not sure where they should go but the download area might be fine for those as well. If you need to upload stuff the instructions are here: Peter -. The transfer is now complete.
I've adjusted the website bugtracker linkto point to github as well.-SLOn 08:43 PM, SiegeLord wrote: It's a very rough lower bound on the number of issues we have, since a good few reside in a TODO list on my desktop, and quite a few are in the ephemeral threads on allegro.cc. Quite a few of the bugs are for Allegro, which we could in principle close, but I'll transfer them as is for now.SL On 11:53 PM, Beoran wrote: The transfer seems fine, but I'm surprised to see that there are so many issues.
After we import them we should probably triage them to see which ones we will and won't implement, and perhaps make new issues that describe the actions better. Kind Regards, B. It's a very rough lower bound on the number of issues we have, since agood few reside in a TODO list on my desktop, and quite a few are in theephemeral threads on allegro.cc. Quite a few of the bugs are forAllegro, which we could in principle close, but I'll transfer them as isfor now.-SLOn 11:53 PM, Beoran wrote: The transfer seems fine, but I'm surprised to see that there are so many issues. After we import them we should probably triage them to see which ones we will and won't implement, and perhaps make new issues that describe the actions better.
Kind Regards, B. As a windows user, i think the InnoSetup script idea is good.not only does it solve a technical problem, it adds a certainprofessionalism to a deployment that makes it seem more than somehobby-game.' Here, have a zip file you unpack, and then install this runtime, andrun this vcdist thing, then click on one of those exe files to launchit. It didn't run. Did you read the README? Didyou follow these 12 steps?. You put it in C:/Program Files/ but itcan't read/write it's own config file.
You have to messabout with permissions in the file system too. ', this isunacceptable these days.On 9/08/2015 8:44 PM, Peter Hull wrote: I've been following the latest speedhack and also reding the recent thread about bundling DLLs/static linking. It seems to me that it's quite tricky to deploy an Allegro game and get it right, especially if the target audience doesn't have allegro at all. Has anyone any ideas on how to make it easier. I was thinking of some sort of simple config file, listing the app's name, exe, resources etc.
Which could be turned into something suitable by a platform-specific processor. For example, on OSX it could work like the 'fixbundle' tool, on Windows maybe generate a WiX or innosetup script.
What do you think? Pete. Attachments:I've been following the latest speedhack and also reding the recent threadabout bundling DLLs/static linking. It seems to me that it's quite trickyto deploy an Allegro game and get it right, especially if the targetaudience doesn't have allegro at all.Has anyone any ideas on how to make it easier. I was thinking of some sortof simple config file, listing the app's name, exe, resources etc. Whichcould be turned into something suitable by a platform-specific processor.For example, on OSX it could work like the 'fixbundle' tool, on Windowsmaybe generate a WiX or innosetup script.What do you think?Pete.
So I explored this further.Here's a test repository where I have transferred all bugs and featurerequests from SourceForge:Some representative issues:allebot is a dummy account I intend to use for transfer to the actualAllegro repository. The way github works, you cannot make comments onbehalf of other users, so all the comments are made by allebot. I triedto make it clear who was the original author with a little header. Thisis the only part that is impossible to change, but many other formatthings I can probably alter.Any comments?-SLOn 07:18 PM, SiegeLord wrote: Should we transfer the bugs from sourceforge to github? I looked into it, and it's in principle possible to do in a minimally lossy way. I can handle the actual work involved, but am looking for any opinions on whether that's something that we should do.
I feel like the reason we don't get that many bug reports via sourceforge (instead, we basically get all of them via allegro.cc) is that its system is a bit of a pain to use, and perhaps we'd get more reports using github's slightly better system.SL. Hi,Allegro has been accepted as a project on Gna!I have created a new mailing list. Please subscribe if you are interested.Subscriptions from the old mailing list will NOT be automaticallytransferred to the new list.I intend to shut down the old list in about one week, then transfer thearchives.
In the mean time, please cross-post messages to both lists.See you there.PeterP.S. Could a couple of interested parties sign up and request to jointhe Gna project (or however it is done) so we have multiple admins.Thanks.