Author Topic: SCI0: Issues implementing Trite Phrase Menu item  (Read 1837 times)

0 Members and 1 Guest are viewing this topic.

Offline Kawa

Re: SCI0: Issues implementing Trite Phrase Menu item
« Reply #15 on: December 09, 2024, 01:20:30 PM »
Like I said, that would be [gExpletive 20] in SCI Companion. gExpletive = 20 defines one variable preset to the number value 20, which is entirely different, while [gExpletive 20] would define gExpletive and then add nineteen more blank slots until the next global variable, which means there's space for 40 characters.

Offline robbo007

Re: SCI0: Issues implementing Trite Phrase Menu item
« Reply #16 on: December 10, 2024, 12:56:04 PM »
Like I said, that would be [gExpletive 20] in SCI Companion. gExpletive = 20 defines one variable preset to the number value 20, which is entirely different, while [gExpletive 20] would define gExpletive and then add nineteen more blank slots until the next global variable, which means there's space for 40 characters.

Aha! I did not know that. Thanks Kawa :)

Its seemed to have resolved the expletive issue. No crashing between rooms any-more :)  But it has also created some bugs with the dying script when using the (Print  (Format @string1 029 47 gExpletive) leaving the room and coming back and trying to die it get some random text added to my view.  I need to troubleshoot it a little more.

Why does the sluicebox code not use this? It only declares it in the main.sc as a local gExpletiveBuffer and gExpletive.

Offline lskovlun

Re: SCI0: Issues implementing Trite Phrase Menu item
« Reply #17 on: December 11, 2024, 12:38:55 AM »
(Print  (Format @string1 029 47 gExpletive)
looks like you need to write @gExpletive instead? But one problem is that we don't have your code, so we are forced to guess all the time. I made some (admittedly vague) references to your variable declarations a long time ago.

Offline robbo007

Re: SCI0: Issues implementing Trite Phrase Menu item
« Reply #18 on: December 11, 2024, 07:13:22 AM »
Right solved.
I was not declaring my string1 correctly. Same problem as Kawa pointed out earlier. I needed to use [string1 40] in the local instead of what I was using string1.

From what I understand was going on here is its placing the gExpletive into string1 and it was not big enough to hold it hence the weirdness with the view naming error.

Code: [Select]
(Print  (Format @string1 029 47 gExpletive)
Thanks again everyone :)


SMF 2.0.19 | SMF © 2021, Simple Machines
Simple Audio Video Embedder

Page created in 0.037 seconds with 23 queries.