View Issue Details
| Category | |||||
|---|---|---|---|---|---|
| SSPBT：本体(SSP) | |||||
| Severity | feature | Reproducibility | N/A | ||
| Status | closed | ||||
| Fixed in Version | 2.5 (リリース) | ||||
| Summary | 0000358: New sakura script tag for unload and load shiori | ||||
| Description | I am steve when debugging shiori, sometimes I need to recompile shiori and put it into ghost for testing, and I think it's stupid to shut down ssp and restart it but there's no function to "uninstall shiori until XXXX happens, then load shiori" or "uninstall shiori and wait X seconds, then load shiori", so I'm wondering if it's convenient to have such a function? I can trigger ghost terminal with commands via vs's generate event, which indirectly allows ghost to trigger the new Sakura script tag when compiling shiori | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
|
|
uninstall -> unload The free time at lunch was a bit tight and I didn't double check the output of the translator |
|
|
Since we have already had "\\![wait,syncobject]" sakurascript tag, you can implement "wait until XXXX happens", so only I need to implement is unload and load shiori tag. [wait,syncobject tag](http://ssp.shillest.net/ukadoc/manual/list_sakura_script.html#_!_wait,syncobject,%E5%90%8C%E6%9C%9F%E3%82%AA%E3%83%96%E3%82%B8%E3%82%A7%E3%82%AF%E3%83%88%E5%90%8D,%E3%82%BF%E3%82%A4%E3%83%A0%E3%82%A2%E3%82%A6%E3%83%88%E6%99%82%E9%96%93_) |
|
|
Is it possible to execute a sakura script via sstp when shiori stops working? I'm trying to figure out how to reload shiori if it goes wrong |
|
|
SakuraScript and SHIORI run independently, so if there is a problem with SHIORI, you can still run SakuraScript using other methods such as SSTP. |
|
|
In the middle of the day it occurred to me, "Why don't I rename this?" And so I did https://github.com/Taromati2/yaya-shiori/commit/58479e7b174c7fd6d68b4222d1af60af99d4b791 Now I can do it all with one click! However, if you can temporarily uninstall shiori you can still optimize the process, so please continue to develop this feature if you can! I just want to say that this feature is not so necessary now and can be lowered in priority You can even turn this off if it is difficult to implement |
|
|
2.5.58 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-11-15 14:43 | guest | New Issue | |
| 2021-11-15 14:52 | guest | Note Added: 0000931 | |
| 2021-11-16 04:29 | ponapalt | Assigned To | => ponapalt |
| 2021-11-16 04:29 | ponapalt | Status | new => feedback |
| 2021-11-16 04:29 | ponapalt | Note Added: 0000932 | |
| 2021-11-16 04:30 | ponapalt | Note Edited: 0000932 | |
| 2021-11-17 13:48 | guest | Note Added: 0000935 | |
| 2021-11-17 13:48 | guest | Status | feedback => assigned |
| 2021-11-17 15:32 | ponapalt | Note Added: 0000936 | |
| 2021-11-17 15:32 | ponapalt | Status | assigned => feedback |
| 2021-12-08 19:50 | guest | Note Added: 0000977 | |
| 2021-12-08 19:50 | guest | Status | feedback => assigned |
| 2022-01-18 13:24 | ponapalt | Status | assigned => confirmed |
| 2022-01-18 15:17 | ponapalt | Fixed in Version | => 2.5 (リリース) |
| 2022-01-27 13:49 | ponapalt | Status | confirmed => closed |
| 2022-01-27 13:49 | ponapalt | Resolution | open => fixed |
| 2022-01-27 13:49 | ponapalt | Note Added: 0001076 |
