Did you tried creating a #Test file with this lines?genome231 wrote:
#Test was included in the vocabulary and simply contained #Random(3, 5), no spaces no anything except that.
Well this test failed sadly :(
Code: Select all
3
4
5
Moderator: 1885

Did you tried creating a #Test file with this lines?genome231 wrote:
#Test was included in the vocabulary and simply contained #Random(3, 5), no spaces no anything except that.
Well this test failed sadly :(
Code: Select all
3
4
5

avatarbr wrote:On a side note, I tried using @Wait( #Random(10, 20)) and did not work too... If this works, I can try using vocabulary.
Code: Select all
@Wait( #Random(10, 20))
No....but I did not put the space before the #Stefaf wrote:Why isn't it working? are you using it inside a Vocab-file?Code: Select all
@Wait( #Random(10, 20))


Great work Stefat and everybody... Thanks for that.Stefaf wrote:Hello everyone!
It's been quite some time, since the last release and now it's done: Patch 54.5

Have you checked the corresponding Apps\Glitter file to be sure certain lines are set up for a single contact?CXZman wrote:Thanks guys !
I was wondering about a bug I noticed : in the Glitter window, the contacts seem to say the other contacts' lines, regardless of who should have been saying what.
Is this a known issue ? Has it been tracked down ?

No Problem - Thanks for testing!avatarbr wrote:Great work Stefat and everybody... Thanks for that.
Just a question, this is the same version you sent me to test?
EDIT: Just downloaded again...it is not the same....I can see the fullscreen mode now


Did you changed something more from the other version (alpha)? I got a freeze with the new version on fullscreen (dont know if this is important) and some strange vocabulary broke lines (not in fullscreen).Stefaf wrote:No Problem - Thanks for testing!avatarbr wrote:Great work Stefat and everybody... Thanks for that.
Just a question, this is the same version you sent me to test?
EDIT: Just downloaded again...it is not the same....I can see the fullscreen mode now
The UI Revision wasn't planned for this version. I was just annoyed about the position calculation Code section. But as soon as i started, i liked it that much, so i decided to put in the current release without asking anyone.^^ I tried to keep it as close to the original, while removing things, i didn't like. Like those misplaced black lines and stuff like that. They simply didn't look right and made the ui looking unfinished.
I hope i'm not the only one.

It is pretty much the same. The GUI rework and some unused objects have been removed. The same compiler and options have been used. So nothing really huge. As long as you don't resize the form or swap to other applications and back (in other words: force to redraw the form), during the tease, no functional code has been altered.avatarbr wrote: Did you changed something more from the other version (alpha)? I got a freeze with the new version on fullscreen (dont know if this is important) ....
avatarbr wrote:...and some strange vocabulary broke lines (not in fullscreen).
I will test again tomorrow (or late) to see if I can get this errors again.
Cross platform compatibility would be a great feature to have. MONO is not really comparable to Wine, but i've taken a look at this and it was horrifying - despite the fact is is designed to run .net applications, there where more than 6000 missing assembly access points to implement. Since it's written in VB.net and not C#.net every single function, method, member and event has to be delegated and interfaced manually. C# compiler is here far more superior.PinkDKB wrote:I'm glad to see that new versions of this are still being released, but is there any word on it being made Linux-compatible?
Or did someone get it to work with Wine? I haven't had any luck in that department.

Oh, I did this. Needed to open the metronome to set the speed (reseted when upgraded) when I was in fullscreen. And open the glitter app again.Stefaf wrote:
As long as you don't resize the form or swap to other applications and back (in other words: force to redraw the form), during the tease, no functional code has been altered.
Could you save the tease and send it to me? Then i can take a look, what's causing the freeze. Tip: When you hold down the Control Key, while clicking suspend session, you can specify a custom location to save the file to.
Or do you use a backgroundimage? I don't know why, but i've noticed, it slows down GDI+ Drawing.
avatarbr wrote:...and some strange vocabulary broke lines (not in fullscreen).
I will test again tomorrow (or late) to see if I can get this errors again.![]()
Tell me more, after testing. I can't imagine, what this means.


yeah, I know...It was me who requested this to 1885pepsifreak wrote:Any missing vocabulary should show up as #Edge(or whatever), not anything else.