[OT] An XFCE launcher that will hide behind Livecode standalones
tore.nilsen at me.com
Mon Mar 7 13:22:48 EST 2016
Or you could just read in the actual stacks to use from a document, put the info into a field, and put a mouseUp handler in the field that responds to the clickLine to launch the chosen stack. Then all you would have to do is to add or change information in the document. You could hav the launcher read from the document automatically in time, or at start up.
> 7. mar. 2016 kl. 19.17 skrev RM <richmondmathewson at gmail.com>:
> That's all very fine in theory until you realise that new standalones will be
> continually added, so one will have to be continually rewriting the launcher and
> reinstalling it, along with the new standalones, on all the machines in my school.
> I have subsequently tired out using an XFCE panel with 6 rows that hides 'always' or 'intelligently',
> which, while not ideal, will probably have to do for the moment.
> In a perfect world (Ha, Ha, Ha) as standalones were added to a folder there would be symbolic links
> added to some sort of blanket launcher/desktop that, on a standalone being launched would not 'hide' or somesuch, but would just remain behind the standalone.
> This can be done by setting up launchers on the XFCE desktop and not having any panels, but
> this has to be done on a machine-by-machine basis which is a 'major fag' frankly.
> On 7.03.2016 02:08, [-hh] wrote:
>> Why don't you write a stack, that has a launch button for each standalone, and minimizes to a small square at topRight after each launch?
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode