I've made a Windows solution to the game distribution process, with automatic creation of the .exe file and everything. It uses the powershell method of archiving.
https://love2d.org/forums/viewtopic.php ... 49#p238749

Inspired by this post, I made a .bat alternative.
https://love2d.org/forums/viewtopic.php ... 49#p238749

When I was learning how to automate the build process for my current game project, I was annoyed with how many steps were involved with all of the solutions everyone else provides. Stuff like LuaRocks and these compilers and other programs. I straight up don't understand how to install and use them....

I don't wanna be rude by arguing, but I have polite disagreements and want to voice them for the last time (and stop clogging the thread thereafter). Looks like it's not too difficult to work around if it bothers you, by setting the 'value' property of either the button or the parent (but not both) ...

Do you have some other suggestion that keeps backwards compatibility? In my opinion, it's a feature not worth keeping nor making backwards compatible, but... If you're gonna do it, you'd need to add a bool that uses the default functionality on false/nil, and not increment the colors for parented b...

I still don't understand. The "Speak" button has the "Chat" input element as parent, while the "A Button" button has no parent, and I don't see a difference between them. [EDIT: You only looked at those two buttons. There're other buttons, like the X buttons in the box...

Can you provide a test case that shows this problem? I don't see anything wrong in the default example. You can see it in the demo, though. Parented buttons default to hilite and hover to focus, whereas regular buttons default to default and hover to hilite. Please note also point 7 here: Edit-butt...

I've created a new Gspot element type called textbutton which utilizes the above attempt-at-programming and applies it to text elements -- for all your text-only-button goodness. The number of work-arounds needed to get this to work with a regular button basically meant rewriting the draw code, whic...

Visual behavior for buttons is a bit weird and unintuitive and lacks any detection of "being mouseddown" in collaboration with the new mouserelease version of click. I've modified the Gspot.button.draw function as so (feel free to collapse the indentation): draw = function(this, pos) if th...

Bug report (and solution): Tooltips applied to larger text elements will render the tooltip-text as small, but will measure the bounds of the box as if they're using the parent's bigger font. Replacing all tooltip-related instances of "element.style.font" with "this.style.font" (...