#61
Posted 04 April 2013 - 01:54 PM
#62
Posted 08 April 2013 - 10:29 AM
#63
Posted 18 May 2013 - 05:34 PM
1. If you say no to run the os on startup, the start won't work.
2. If you try to run startup it freezes. (lol, I was trying to run lyquidOS within lyquidOS :3
#64
Posted 21 May 2013 - 02:21 PM
#65
Posted 25 May 2013 - 01:12 AM
Lyqyd, on 30 October 2012 - 12:24 AM, said:
Maybe let people put & or another symbol after the program name and arguments to keep it open. Or maybe a checkbox?
#66
Posted 25 May 2013 - 02:38 AM
pcall(shell.run, table.concat({...}, " ")) os.pullEvent("key")
You'd use that from the run prompt and pass the command you actually wanted to run as arguments. It should run the program you pass it, safely ride out any crashes or errors, then wait for a key press before ending (and therefore closing the window). I can build this in as a program in future versions.
#67
Posted 25 May 2013 - 06:19 AM
#68
Posted 25 May 2013 - 06:57 AM
if not term.isColor() then nonColorMode else colorMode() endThats just what i had in mind
#69
Posted 25 May 2013 - 02:34 PM
EthanAG, on 25 May 2013 - 06:57 AM, said:
if not term.isColor() then nonColorMode else colorMode() endThats just what i had in mind
There are only two places in LyqydOS that make isColor() checks. Both of them do exactly the same thing:
if process.windowCompositor.target.isColor() then pTable.window:setType("standard") pTable.window:setDecorations("pretty") end
#70
Posted 22 June 2013 - 02:18 AM
#71
Posted 22 June 2013 - 02:42 AM
#72
Posted 30 June 2013 - 01:06 AM
Also new in this release is the debug utility that superaxander suggested. The usage is simply to prepend "debug " to the command/program you want to try to run. This will hold open the window it runs in until after a key is pressed once the program has stopped running. That allows a developer to view error messages their program throws under LyqydOS.
I've updated the other two screenshots in the original post to reflect the new appearance and features, including a shot of the "ps" program in action. You can see the process ID and the program's path for each running process. Note that not every process has a window (lws, for example) and that the lua window in that shot is minimized.
Most users who have the installer file still should be able to update simply by re-running it, as it will fetch a new copy of the installer before attempting to install.
#73
Posted 30 June 2013 - 04:57 AM
Lyqyd, on 30 June 2013 - 01:06 AM, said:
Also new in this release is the debug utility that superaxander suggested. The usage is simply to prepend "debug " to the command/program you want to try to run. This will hold open the window it runs in until after a key is pressed once the program has stopped running. That allows a developer to view error messages their program throws under LyqydOS.
I've updated the other two screenshots in the original post to reflect the new appearance and features, including a shot of the "ps" program in action. You can see the process ID and the program's path for each running process. Note that not every process has a window (lws, for example) and that the lua window in that shot is minimized.
Most users who have the installer file still should be able to update simply by re-running it, as it will fetch a new copy of the installer before attempting to install.
#74
Posted 20 July 2013 - 02:28 AM
#75
Posted 20 July 2013 - 11:41 PM
Like how you can have multiple windows and how you can resize, minimize and all that. Nice job.
P.S. Don't worry, I won't steal your ideas or work. Have fun and happy coding.
#76
Posted 27 July 2013 - 05:11 PM
#77
Posted 27 July 2013 - 11:34 PM
#78
Posted 24 August 2013 - 01:06 PM
#79
Posted 24 August 2013 - 01:19 PM
Edit: Turns out I had incorrectly placed some Y-bounding checks! I fixed that and now luaide seems to start up fine on any resolution. Obviously, since it doesn't handle window_resize events, it doesn't redraw immediately, so it's probably best to relaunch it after the initial resize.
#80
Posted 08 September 2013 - 04:36 PM
Couple of things...
1. The "-" button seems to be the default "Crash the OS" button.
2. When you press Enter with nothing typed in the Run Program window, the window goes away but won't come back again.
3. Monitor_touch events still get sent to all open windows. Probably won't be an issue until you support multiple monitors... When might that be?
Again, really nice piece of work here, Lyqyd. I'm duly impressed.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users