Front End Support > MaLa Frontend
MaLa Plug-In Dev's.. We have our own Forum Section
loadman:
--- Quote from: squirrellydw on February 07, 2007, 09:22:07 pm ---what is the Malastub?
--- End quote ---
It is a 'Kewl Tewl' to assist Plug-in Developers from having to Launch/quit MaLa just to test things on their plug-ins.
It will also save me changing my personal MaLa set-up all the time just for testing purposes
This KICKS BUTT!
I love it
It will save me a lot of pain loading and Quitting MaLa to test stuff
I just tried it with two Plug-ins
I am going to use this a lot
As you pointed out in your doc. Some Plug-in's expect things in a certain order
Two suggestions:
1) Can you have an option that only enables buttons in order?
eg You have to hit 'Mala Start' before the others are enabled, All buttons are dimmed when you hit Screensaver start until you hit screen saver stop etc etc and you have to hit 'Mala Quit' before you quit your ap?
2) Changing selected Plug-ins sometimes crashed your ap. Mainly a problem with the more complex Led-Wiz ap (no big deal) . You just have
Also I think Swindus is planning to add a new trigger 'current screen orientation' to the next version. Can future additions like that easily be added to your app?
Thanks
Load
fatfingers:
--- Quote from: loadman on February 07, 2007, 09:11:02 pm ---
--- Quote from: arzoo on February 07, 2007, 07:27:12 pm ---loadman,
With a bit of help from AltaVista Babel Fish, I was able to register and post to the new Mala Plugin forum! ;D
I've posted my MaLa Stub test app. For those interested, here's the link - MaLaStub.zip
--- End quote ---
Good Work :applaud:
I use: http://www.google.com.au/language_tools?hl=en
I don't use it much anymore. You quicky get an idea
--- End quote ---
I found that hovering over most items will show the link at the bottom and the link is usually pretty descriptive and in English! ;D
arzoo:
loadman,
Thanks for the props!
I had considered adding logic to enable the event buttons in some order, but each plugin is different - for example, the Mature plugin doesn't even require the Mala Start event. In the end, I just decided to let the user make or break the plugins. :dizzy:
It should be no problem adding any new events or event data that swindus adds to MaLa.
loadman:
--- Quote from: arzoo on February 07, 2007, 10:27:57 pm ---loadman,
Thanks for the props!
I had considered adding logic to enable the event buttons in some order, but each plugin is different - for example, the Mature plugin doesn't even require the Mala Start event. In the end, I just decided to let the user make or break the plugins. :dizzy:
It should be no problem adding any new events or event data that swindus adds to MaLa.
--- End quote ---
Kewl... I will just be careful :P
:notworthy: :notworthy: :notworthy:
I read the readme properly and noticed you can have it fire up automatically fire up within the BDE without re-naming the dll to mplugin
Super Helpful to me. I feel I should make a donation to the arzoo Beer fund or something.
loadman:
I guess we should close this thread soon and use the new forum :dunno
anyway....
--- Quote ---Installation
------------
MaLaStub.exe uses the same folder structure as MaLa.exe. All plugins (*.mplugin) should reside in a sub-folder called 'Plugins'. It will also detect any DLL (*.dll) in the same folder as MaLaStub.exe.
--- End quote ---
I am having a minor prob with this...
It finds the *mplugins and *dll's in a subfolder called 'plugins
But it does not seem to find *.dlls in the same folder as MaLaStub.exe so using it to auto run with delphi does not find the *.dll's
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version