Re: xVariable max 1024 bytes ?
"Dimitris Keletsekis [email protected] [gui4cli]" <[email protected]> Wed, 14 May 2014 19:38:10 +0300
| Newsgroups | gmane.comp.windows.gui4cli |
|---|---|
| Message-ID | <CAHiKg1XbV4DSFTyHNzSn3gJ_rz11-W5HaB5ZN64HWr4WX6+Wkg@mail.gmail.com> |
Correct (I should have told you that). If you set the variable in a command, then you're ok because you can do it after you set the buffers. Dimitris On Wed, May 14, 2014 at 5:19 PM, [email protected] [gui4cli] < [email protected]> wrote: > > > > Aah, now I understand it a bit. So this doesn't count for normal variables? > I mean; if I set the buffers right and have the whole xVariable content in > a normal single string like... > > mySmallGui = 'all the gui stuff' > > and then use e.g. addCode $mySmallGui, there would be no problem? > > Funny that in all the years I use xVariables they never have been larger > than 1024 bytes :) > > Chris > > > ---In [email protected], <gui4cli@...> wrote : > > > Set buffers is a command so it will be executed after the script is > parsed, whereas the starting state of the xVariable is set while the script > is being parsed. > > You can have a launcher gui, as mentioned, or I could add a "#Buffers" > parser command (like #include), to set them on the fly. I'll have a look. > > Dimitris > > > > >