Page 9 of 121

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Mon Jan 06, 2014 2:01 pm
by altce
Memory leak is reduced to 5 MB per picture on average
(using skirmish) and Guideme v 0.06...
Much better but still something to fix....

Ending using the exit button does not unload javaw.exe ,
nor the DOS window it opens with start.bat.

VB6 Serial port code:

Code: Select all

 Initialize function (once library is loaded)Private Function connect(settings As String, port As Integer, port_open As Boolean)   If RADI.PortOpen = False Then      RADI.CommPort = 1      RADI.settings = "9600,n,8,1"      RADI.PortOpen = True      RADI.InputMode = comInputModeBinary      Else      RADI.PortOpen = False   End If  End Function or INLINE    RSDAT.CommPort = 3   RSDAT.settings = "9600,n,8,1"   RSDAT.PortOpen = True   RSDAT.RThreshold = 0 Sending  hex data outhex = &HECRSDAT.Output = outhex sending strings: RSDAT.Output = RS232$ & VbcrlfRSDAT.Output = "hello world" 
Keep on the good work.

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Mon Jan 06, 2014 7:48 pm
by philo
meson1 wrote:Also, is there a way in js to get the current page id?
yes
guideSettings.getPage()

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Mon Jan 06, 2014 9:01 pm
by philo
Baron Hardpenis von Steele wrote:I tried to use the 'selected' attribute on an <option> form element and it broke.
I have tested it and it worked for me
it needed to be a proper attribute selected="" just selected on its own caused an error.

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Mon Jan 06, 2014 11:12 pm
by meson1
philo wrote:
meson1 wrote:Also, is there a way in js to get the current page id?
yes
guideSettings.getPage()
Excellent except ...

During the pageLoad() event, guideSettings.getPage() is still set to the previous pageid.

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Tue Jan 07, 2014 12:52 am
by NeverSay
Anyone have a temp direct link to this my internet wont let me dowload from either source :(

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Tue Jan 07, 2014 11:24 pm
by philo
NeverSay wrote:Anyone have a temp direct link to this my internet wont let me dowload from either source :(
If it is not allowing you to down load from either then there is probably an issue at your end.
What error are you getting when you try to download?

Also are you looking for 32 or 64bit?

I am currently working on the memory leaks and will put a new version out soon anyway.

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Thu Jan 09, 2014 8:46 pm
by philo
Version 0.0.7
Heap and thread leaks fixed
CSS node can now be multi line
Error handling for scriptvars that are not converted to strings causing text not to display
Global JavaScript node
<GlobalJavascript><![CDATA[
function gAll() {
overRide.addButton("start", "Restart","", "", "", "");
}
]]></GlobalJavascript>
<Pages>


You will need an existing version of GuideMe and over write with the new GuideMe.jar
(I have also included the files new in 0.0.6 you will only need them if you don't have them already)
https://mega.co.nz/#!9VxC2ATa!ReBo6k5wJ ... OUDtovTM70

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Thu Jan 09, 2014 11:46 pm
by meson1
Hi Phil

Did you happen to look at the JS pageid issue I mentioned above?

Also, a question: how do you set and unset flags in JS?

Also, also, :-) did you know that when you have <AutoSetPageWhenSeen> set to true. it adds pageids without checking if they are there first, so if you loop round the same page multiple times, you end up with a huge long list of that pageid in the flag string.

It doesn't happen for flags set using the xml "set=" clause. If I do a set="wibble" multiple times in the xml guide, I only ever end up with one "wibble" in the flag string which is what I expect. But <AutoSetPageWhenSeen>true swamps the flag string with multiple instances of the same pageid. So perhaps this might be something worth tightening up when time allows. :-)

Kindest regards

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Fri Jan 10, 2014 10:22 pm
by philo
meson1 wrote:Hi Phil

Did you happen to look at the JS pageid issue I mentioned above?

Also, a question: how do you set and unset flags in JS?

Also, also, :-) did you know that when you have <AutoSetPageWhenSeen> set to true. it adds pageids without checking if they are there first, so if you loop round the same page multiple times, you end up with a huge long list of that pageid in the flag string.

It doesn't happen for flags set using the xml "set=" clause. If I do a set="wibble" multiple times in the xml guide, I only ever end up with one "wibble" in the flag string which is what I expect. But <AutoSetPageWhenSeen>true swamps the flag string with multiple instances of the same pageid. So perhaps this might be something worth tightening up when time allows. :-)

Kindest regards
Version 0.0.8 (overwrite your current GuideMe.jar with this one)
Fix for autopage spawning multiple identical flags
Current Page and Previous page available to javascript
Access to set, unset and test for flags

https://mega.co.nz/#!MdACnIYK!T5FFzDElj ... tygLRscITA

Code: Select all

//Returns true or false (this is the code that is used  within guideme so ifset/ifnotset handle and/or conditions as they would in the xml)comonFunctions.canShow(guide.getFlags(), String ifSet, String ifNotSet); //flagNames is a comma separated list e.g."page3,page5" or "page3"  comonFunctions.SetFlags(String flagNames, guide.getFlags());comonFunctions.UnsetFlags(String flagNames, guide.getFlags()); guideSettings.getCurrPage();guideSettings.getPrevPage(); htmltext = htmltext + "Current Page is " + guideSettings.getCurrPage() + " <br/>";htmltext = htmltext + "Previous Page is " + guideSettings.getPrevPage() + " <br/>";            jscriptLog("Flags " + comonFunctions.GetFlags(guide.getFlags()));jscriptLog("Can show ? " + comonFunctions.canShow(guide.getFlags(), "start", "fluffy"));comonFunctions.SetFlags("fluffy", guide.getFlags());jscriptLog("Flags " + comonFunctions.GetFlags(guide.getFlags()));jscriptLog("Can show ? " + comonFunctions.canShow(guide.getFlags(), "start", "fluffy"));comonFunctions.UnsetFlags("fluffy", guide.getFlags());jscriptLog("Flags " + comonFunctions.GetFlags(guide.getFlags()));jscriptLog("Can show ? " + comonFunctions.canShow(guide.getFlags(), "start", "fluffy"));            2014-01-10 20:57:22,986 INFO  Jscript - Starting Flags {[start, Page1a, Page1]}2014-01-10 20:57:23,058 INFO  Jscript - Flags start,Page1a,Page12014-01-10 20:57:23,059 INFO  Jscript - Can show ? true2014-01-10 20:57:23,059 INFO  Jscript - Flags start,Page1a,fluffy,Page12014-01-10 20:57:23,059 INFO  Jscript - Can show ? false2014-01-10 20:57:23,060 INFO  Jscript - Flags start,Page1a,Page12014-01-10 20:57:23,060 INFO  Jscript - Can show ? true2014-01-10 20:57:23,060 INFO  Jscript - Ending Flags {[start, Page1a, Page1]}

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Fri Jan 10, 2014 11:03 pm
by meson1
philo wrote:Version 0.0.8 (overwrite your current GuideMe.jar with this one)
Fix for autopage spawning multiple identical flags
Current Page and Previous page available to javascript
Access to set, unset and test for flags

https://mega.co.nz/#!MdACnIYK!T5FFzDElj ... tygLRscITA
By eck! It's Christmas all over again. :-D Stupendous.

Thanks, man.

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Sat Jan 11, 2014 3:33 pm
by d3vi0n
I'm back :w00t: But the new updates 0.0.6, 0.0.7 and 0.0.8 don't work... :\'-( :no: :huh:

I copied them into the main folder: overwriting GuideMe.jar, adding userSettingsUI.xml and adding the folder /userSettings. Result: Menu "Application Preferences" has now no emtries for Data Directory or Name anymore. Userpreferences loads userSettingsUI.xml but the images are missing and page 2 stays blank (error?).

Do i miss something? :huh:

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Sat Jan 11, 2014 8:03 pm
by Hardyyz
Is there a list of teases somewhere? or is there only like those 4 from the 1st page available? and also can i use teaseme teases with this thing?

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Sat Jan 11, 2014 10:44 pm
by philo
Hardyyz wrote:Is there a list of teases somewhere? or is there only like those 4 from the 1st page available? and also can i use teaseme teases with this thing?
Alpha test is where the developer tests it
Beta test is where it goes out to be initially tested, Guideme is in it's very early stage, so there are not many teases written specifically for it yet.

TeaseMe teases should work in GuideMe, if you find one that works in TeaseMe but not in GuideMe, then you can post in this thread and I will try to make sure it works in the next version.

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Wed Jan 15, 2014 6:29 pm
by MisterMark88
Nice work at improving and delevoping GuideMe. Also great you shared the sources at GitHub.

I am a developer and my main system is Ubuntu, since you aren't offering Linux builds of GuideMe I grabbed the source and tried to build them myself.
However I couldn't manage to build because you used some teases for unit tests I can't find around at Milovana. A tribute to Jurgita Valts and SWTPortTest (witch I asume isn't a tease but a handmade file)
Since my current build (without testing) isn't working as expected it would be nice if you could publish those files for the unittest so I can start debugging and maybe help improving GuideMe.

Re: GuideMe (TeaseMe v2.0): BETA Thread

Posted: Wed Jan 15, 2014 6:37 pm
by xeenith
I was playing around with the skirmish tease when I noticed the last versions included a problem with the metronome (didn't have time to touch it since 0.5 I think so I don't know which patch changed it)

the varying of the metronome speed doesn't work anymore, I modified it to start at 120 instead of 60, but even one encounter with heat increase that put the speed from 120 to nearly 300, the metronome itself didn't register the change.
I tried to quit the program and start it up anew, the tease continued from the last slide, with the right speed this time, but as soon as the slide changed, it was back to 120. I didn't modify the tease file yet, and it was working fine the last time I tried it, so something in the patch notes must have changed the way some variables are used or set.

anyone playing around with it noticed something like that ?