Show Posts

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.


Topics - BOXXMAN

Pages: [1]
1
Scripting / Getting MultiMon Script to Work?
« on: July 24, 2017, 09:23:29 PM »
No matter what settings I try,  I cannot get this script to show any artwork on any monitor. What am I doing wrong? Does anyone else have this working and can offer advice? 

2
How would you go about sending variables to external AHK scripts for example. In Hyperspin, you could use "%romname%" and "%systemname%" to send variables to an AHK script. You could also use the clipboard function in AHK to capture variables and then copy them to your script. However, with AM, or I don't know how you can extract those variables to use with scripts that aren't written in squirrel. I am much more comfortable with writing AHK scripts to automate a lot of things, and would rather do that than use squirrel scripts. So is it possible to get the variables and pass them to AHK, or anything else for that matter? If squirrel had some sort of function that could just copy variables to the clipboard that would work, so they could then be copied into another application.

3
Scripting / What is the usage of fe.Monitor command?
« on: July 20, 2017, 09:43:13 PM »
There is very little documentation as to how you communicate with other monitors that I can find. In the documentation of layouts all it mentions is
#### `fe.Monitor` ####
This class represents a monitor in Attract-Mode, and provides the interface to the extra monitors in a multi-monitor setup. Instances of this class are contained in the fe.monitors array. This class cannot otherwise be instantiated in a script.

Ok, so how do you implement this in a layout? Can you classify monitors as 1,2,3, ect, and send different artwork to each one? As it is, I have multiple monitors enabled, and fill screen mode. Like this, I can have a large layout that spans two monitors, and my layout displays marquees and game info on the secondary, which is nice. It gives the appearance that you have two separate displays running, but in reality it is just one extended display. However, the images on the secondary monitor won't hold after you launch a game, since AM suspends itself and turns the secondary monitor white after a game is launched. So, does anyone know if you can have multiple monitors running separately from each other rather than just an extended desktop?

4
General / Can Mouse Pointer Be Made Visible?
« on: July 04, 2017, 08:44:16 AM »
I'm doing something where I'd like the mouse pointer to be visible in the FE. How can you enable in .cfg file? I can,t find an option to enable it anywhere.

5
Scripting / Can you use [Overview] info in displays menu?
« on: June 13, 2017, 06:59:16 PM »
Is it possible to use the [Overview] for system information on displays menu? I tried creating a .cfg file with the system name, in the same format as rom info, and put it in romlist system folder, but it did not work. Is there a way to do this, because I want to be able to display console information on the system display menu. Also, is it possible to use more than one font in a layout?

6
General / Can someone explain the "Utility Menu"
« on: June 12, 2017, 11:57:59 PM »
Forgive my ignorance, but I don't seem to grasp what you can do with the Utility Menu plugin. I see that you can use it to launch other scripts, but is that all it does? It says you can run commands, but does that mean it can run executables by simply filling in the the path and .exe, or do you use a command like fe.plugin_command("MyProg.exe","") to run?  Nothing I've tried like that has managed to launch or do anything, so does it only run other scripts only?

7
Scripting / Passing command line arguments within a layout [SOLVED]
« on: May 25, 2017, 04:15:08 PM »
How would you go about passing system and rom information as variables to a command line? For example, I am trying to use Rocketlauncher in a layout to bring up the pause menu for the current game in the display by using

fe.plugin_command("/Rocketlauncher/Rocketlauncher.exe", -s [system] -r [name] -p AttractMode -m pause");

However, if I try to pass arguments as magic tokens (which I'm assuming is wrong) in [brackets] it doesn't work. I have also tried enclosing in quotes ["name"], and "[name]", plus just about every way i can think of with or without brackets and quotes. Everything either shows up as a literal string, or crashes the layout. What is the correct way to get these parameters and pass them as arguments? The frontend itself seems to have no problem doing it when inputting the arguments to set up the emulator. Also, it would be appreciated if you could point me in the right direction how to add this of some sort of function that can be called on when one of the "custom" buttons is pressed. Thanks for any help with this. :-[

Pages: [1]