wthit56

joined 11 months ago
[–] [email protected] 1 points 5 months ago

I've used the AI text plugin a fair bit, but have never seen something called textStream. And it's not listed on the plugin page. Where can I actually find it?

[–] [email protected] 2 points 5 months ago (2 children)

When you're talking about "textStream" and such... I'm not sure what you're referring to, and I'm quite familiar with the plugin. Is that only talking about something to do with text-to-speech?

[–] [email protected] 1 points 5 months ago

You're just pasting a url to set the avatar, right? You can get the url of any image you see by right-clicking it, so kinda makes sense this would be possible. They could even download the avatar image, upload it somewhere, and use that new url instead.

There's never in the history of the internet and avatars been a way of stopping someone using the same avatar image as you.

[–] [email protected] 2 points 5 months ago
[–] [email protected] 2 points 5 months ago

Oh interesting. Must use a hash or something...

[–] [email protected] 2 points 5 months ago (2 children)

Heads up: that first jpeg link works fine for me.

[–] [email protected] 2 points 5 months ago (1 children)

Sounds like it's basically reminding the AI of some data each time a prompt is sent to it. What I do is just put it in the prompt, and it seems to work fine.

Those generators you listed all do the same, reminding the AI of things it needs to know about, but are pretty complex and have a lot to send, most likely. You can make your own Text AI pretty easily, and send whatever you like with the prompt. Maybe try that.

[–] [email protected] 7 points 6 months ago

Thanks for the update! I get it. It's a lot of work, and a balancing act for timing things as well. It's hard to live up to (a minor group of) people's expectations. But knowing what the state of play is with an update like this really helps 👍

[–] [email protected] 1 points 6 months ago

It's difficult. Because it's generally trying to make one image, building from one idea.

You can try using the BREAK keyword to separate groups of meaning. Like blue hat BREAK yellow dress is more likely to not mix up the colours for the skirt and hat.

[–] [email protected] 1 points 6 months ago

The key is, $output is a function. With properties set on that function. So, that requires some sort of build to happen when you first access $output. Your test doesn't have any of that, which is why it works ;p

Here's an example of properties not working correctly on an $output function: https://perchance.org/sqfppqoq6e#edit I did try various tweaks and workarounds. Got something working within the page (can't remember how that worked now) that didn't work when imported. But this example doesn't even work within the page.

[–] [email protected] 1 points 6 months ago

In another comment on this post I talked about my own expectations.

And that example I linked to in the post has some very weird behaviour being demonstrated.

 

Helper functions to add and remove children from a Perchance list.

1
submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]
 

My newer generators are not having their screenshots generated. https://perchance.org/perchance-object-reference

Though this one works somehow: https://perchance.org/list-management-plugin

They're using the same formatting and scripts for the page as all my others.

 

Currently it's quite fiddly, making sure all the keys/names arrays are up to date so it still functions as expected.

If it used a set and delete handler it could handle all that internally. Or if there was some special methods we could use like .addValue() and it would figure out what kind of value it is--property, node, function--and handle it correctly.

Of course, I'm working on a plugin now to handle this for people. 😜

 

There's a lot of stuff that becomes real fiddly to do because they are not iterable... that would be real easy to do if they were iterable. I believe there's a proxy "trap" for iterating over properties somewhere in there.

 

This plugin overrides the device's color scheme, but uses the existing styles. No changing of styles is needed whatsoever; it just works.

 

Most likely SUPER not a priority. But you know me 😅

https://perchance.org/prompt-style-tester#edit

The "go" button updates the entire page. As the options are generated this means they are re-generated, which means the chosen option resets, and you can only ever test the top option: Painted Anime.

Simple fix though: put a div with an id around the generations, then update that div only. That's all that needs updating anyway.

 

As we have ignorePerchanceErrors() and clearPerchanceErrors(), seems fair to have this function too, for public use.

 

Would be useful to be able to see the images just in the page so we don't accidentally delete the wrong one, stuff like that. I know we can click on the link, but this would just be a nice feature to make it easier.

 

Another day, another learn...ing...s.

This covers everything from how to start editing/making a generator, to writing perchance code. (The more web-y stuff are covered in my other tutorial.)

 

Seems to be related to this: ___htmlToElements(). It takes a string which is the text, ignoring the fact that HTML entities are not normal characters and should not be interpreted as normal HTML. For example, &lt; will be interpreted as < which can open a tag.

Example: https://perchance.org/qzi72h52te#edit

So if an element contains any perchance code, and HTML entities, the HTML entities are essentially lost and become real characters. Which isn't what you want if you're trying to present plain-text code to the user.

Definitely does not work as expected at least.

 

For example, I'm linking to the Learn tab but that doesn't actually open the Learn tab.

 

No error message makes it to the display.

In the console there is:

Critical error in __createPerchanceTree: TypeError: Cannot read properties of undefined (reading 'startsWith')

And in the error messages there's just this:

Your generator's script seems to have errors in it. If you haven't recieved any other errors above this one which could indicate what went wrong, then this could be a bug in the Perchance engine. *etc...*

("recieved" should be "received" by the way 😜)

view more: ‹ prev next ›