Has there been any plans to add the ability to create windows that are not "mini"? In other words, not restricted to being inside of the main MUSHclient window. I have an entire 32" tv connected to my laptop going to waste where I could draw the map or other things while I'm at home. Maybe just add an option to MiniWindow for it to be drawable outside of MUSHclients real estate?
exWindow
Posted by Kevnuke on Fri 05 Oct 2018 06:37 AM — 4 posts, 19,915 views.
Due to the underlying architecture this would be very hard. The simplest work-around for you would be to run two copies of MUSHclient, and have one moved to the other monitor.
Then you could use UDP or TCP to send messages from the main world to the map world to update what it is displaying. There are some examples of using UDP here:
Or you could use LuaSocket to send TCP messages from one copy of the client to another.
Then you could use UDP or TCP to send messages from the main world to the map world to update what it is displaying. There are some examples of using UDP here:
Please see the forum thread: http://gammon.com.au/forum/?id=4951.
Or you could use LuaSocket to send TCP messages from one copy of the client to another.
Does MUSHclient know the size of the display it's currently on or would it retrieve the size of the laptop screen? I'm just wondering in case I need to send data back to client1 for some reason.
Also, is there a way to put MUSHclient into a type of reading mode where the output buffer takes up the whole screen, so even the title bar goes away, but not the Info bar and such. Those might still be useful.
Oh that just gave me an idea! The ability to enable more than one Info/Status bar. I guess make the default Info/Status bars 0 so it doesn't break existing code and the others numbered. Or be able to divide the existing ones into sections so you could have different things displayed in each section without concatenating a bunch of things together and not knowing how long each will be or how much time before each item gets new data. Like, passes it a argument telling it how many pixels wide or what percentage of the total bar a section is. Or maybe do both!
Sorry, that was a lot for one post..
Also, is there a way to put MUSHclient into a type of reading mode where the output buffer takes up the whole screen, so even the title bar goes away, but not the Info bar and such. Those might still be useful.
Oh that just gave me an idea! The ability to enable more than one Info/Status bar. I guess make the default Info/Status bars 0 so it doesn't break existing code and the others numbered. Or be able to divide the existing ones into sections so you could have different things displayed in each section without concatenating a bunch of things together and not knowing how long each will be or how much time before each item gets new data. Like, passes it a argument telling it how many pixels wide or what percentage of the total bar a section is. Or maybe do both!
Sorry, that was a lot for one post..
Kevnuke said:
Does MUSHclient know the size of the display it's currently on or would it retrieve the size of the laptop screen? I'm just wondering in case I need to send data back to client1 for some reason.
Does MUSHclient know the size of the display it's currently on or would it retrieve the size of the laptop screen? I'm just wondering in case I need to send data back to client1 for some reason.
Try:
GetSystemMetrics
The documentation for the GetSystemMetrics script function is available online. It is also in the MUSHclient help file.
Kevnuke said:
Also, is there a way to put MUSHclient into a type of reading mode where the output buffer takes up the whole screen, so even the title bar goes away, but not the Info bar and such. Those might still be useful.
Also, is there a way to put MUSHclient into a type of reading mode where the output buffer takes up the whole screen, so even the title bar goes away, but not the Info bar and such. Those might still be useful.
Not really, you can make the command window very small though.
Kevnuke said:
Oh that just gave me an idea! The ability to enable more than one Info/Status bar. I guess make the default Info/Status bars 0 so it doesn't break existing code and the others numbered. Or be able to divide the existing ones into sections so you could have different things displayed in each section without concatenating a bunch of things together and not knowing how long each will be or how much time before each item gets new data. Like, passes it a argument telling it how many pixels wide or what percentage of the total bar a section is. Or maybe do both!
Oh that just gave me an idea! The ability to enable more than one Info/Status bar. I guess make the default Info/Status bars 0 so it doesn't break existing code and the others numbered. Or be able to divide the existing ones into sections so you could have different things displayed in each section without concatenating a bunch of things together and not knowing how long each will be or how much time before each item gets new data. Like, passes it a argument telling it how many pixels wide or what percentage of the total bar a section is. Or maybe do both!
That's what miniwindows are for these days.