http://tech.groups.yahoo.com/group/Amulet/ Amulet Easy GUI Users Group Wed, 11 Nov 2009 10:27:36 GMT plaingent http://tech.groups.yahoo.com/group/Amulet/message/1571 http://tech.groups.yahoo.com/group/Amulet/message/1571 I've noticed the Amulet:back() function is implemented using a stack. It would be useful to be able to go back 2 steps, perhaps back(n)? I could do this with Tue, 10 Nov 2009 18:15:32 GMT Jim Weber http://tech.groups.yahoo.com/group/Amulet/message/1570 http://tech.groups.yahoo.com/group/Amulet/message/1570 Yes, that is obviously a bug that needs to be fixed in the next release. Thanks for letting me know. Jim Weber Lead Firmware Engineer Amulet Technologies Tue, 10 Nov 2009 09:55:27 GMT fairy_dave http://tech.groups.yahoo.com/group/Amulet/message/1569 http://tech.groups.yahoo.com/group/Amulet/message/1569 I'm only using 0.0.8 but I've recieved the same error in the compiler. Mon, 09 Nov 2009 19:42:52 GMT maltman01 http://tech.groups.yahoo.com/group/Amulet/message/1568 http://tech.groups.yahoo.com/group/Amulet/message/1568 Jim, First of all I am using the new GEM Color Starter Kit, just to make sure we're clear on this. You're online document dated 10/01/2009 under the Amulet Mon, 09 Nov 2009 17:38:50 GMT Jim Weber http://tech.groups.yahoo.com/group/Amulet/message/1567 http://tech.groups.yahoo.com/group/Amulet/message/1567 In the Amulet Color Chip there are 256 different 26-character string variables. In the older monochrome chip there are 199 18-character string variables. The Mon, 09 Nov 2009 14:23:08 GMT maltman01 http://tech.groups.yahoo.com/group/Amulet/message/1566 http://tech.groups.yahoo.com/group/Amulet/message/1566 I'm a little confused with the internal ram string variables. Part of the documentation indicates that there are 256 different 26-character string variables Mon, 09 Nov 2009 02:45:30 GMT fairy_dave http://tech.groups.yahoo.com/group/Amulet/message/1565 http://tech.groups.yahoo.com/group/Amulet/message/1565 That will probably do the trick. I think it just means I need to rethink my approach to this concept. These screens were going to be less of a pop-up and more Fri, 06 Nov 2009 18:19:54 GMT Jim Weber http://tech.groups.yahoo.com/group/Amulet/message/1564 http://tech.groups.yahoo.com/group/Amulet/message/1564 Dave, How long were the strings you were wanting to send? How many InternalRAM string variables are you going to be using? We use dynamic popup screens with Fri, 06 Nov 2009 12:27:41 GMT fairy_dave http://tech.groups.yahoo.com/group/Amulet/message/1563 http://tech.groups.yahoo.com/group/Amulet/message/1563 Hmm that's quite a limitation. Had been hoping I could provide dunamic popup screens with text from the controller but now I'll need to reduce the length of Thu, 05 Nov 2009 12:44:06 GMT Robert Smith http://tech.groups.yahoo.com/group/Amulet/message/1562 http://tech.groups.yahoo.com/group/Amulet/message/1562 Finally, a question that is not related to the Gem compiler (I think). I am not sure which compiler you are using; if you are using compilers 3.x, read the Thu, 05 Nov 2009 12:30:28 GMT palmdetective http://tech.groups.yahoo.com/group/Amulet/message/1561 http://tech.groups.yahoo.com/group/Amulet/message/1561 hi; if your using a string widget to display the string, their default character length is 25 characters. Use the printf parameter to change the length of the Thu, 05 Nov 2009 07:32:58 GMT fairy_dave http://tech.groups.yahoo.com/group/Amulet/message/1560 http://tech.groups.yahoo.com/group/Amulet/message/1560 I forgot to mention... If I set the next string along in memory and read back the origional string then I'll wind up reading the first 26 characters from the Thu, 05 Nov 2009 07:20:32 GMT fairy_dave http://tech.groups.yahoo.com/group/Amulet/message/1559 http://tech.groups.yahoo.com/group/Amulet/message/1559 Greetings all, I'm trying to send some long(er than my usual length) strings to the Amulet. I can send them and read them back no worries. When I try to Wed, 04 Nov 2009 23:08:35 GMT fairy_dave http://tech.groups.yahoo.com/group/Amulet/message/1558 http://tech.groups.yahoo.com/group/Amulet/message/1558 I'm keeping the communications minimal so I decided to keep the buttons always updating. The flicker isn't visible unless you're at an angle to the screen so Tue, 03 Nov 2009 14:28:36 GMT maltman01 http://tech.groups.yahoo.com/group/Amulet/message/1557 http://tech.groups.yahoo.com/group/Amulet/message/1557 Dave, Have you tried to use an InternalRam byte as a flag for the comparison? Have the controller change the button string variable and then set the byte flag