Temporary Forum Oddities

[Kernelpanic]

@grymmjack -  Plug-ins will never be as good unless made by same caliber of developer as that which they plug-in to.

This reminds me of a saying: "If you want something to be really good, make it yourself!"

[SMcNeill]

@grymmjack -  Plug-ins will never be as good unless made by same caliber of developer as that which they plug-in to.

This reminds me of a saying: "If you want something to be really good, make it yourself!"

Working with forum plugins reminds me of an old saying as well: "Two steps forward, one step back."  

Every time we implement a couple of new things, half of them end up having to be reverted as they just won't work properly without glitching out somewhere, or bugging out something else that we'd installed previously.  Honestly, it truly does seem like that for every two plugins we install (two steps forward), we end up having to remove one of them (and that's the step back).

Who knew programming was so much like a line dance sometimes??

[grymmjack]

I just saw the following error while commenting (it works, but you don't see any icons):

I was going to report on this last night, instead of my actual post, but I thought it was a problem at my end. (Manjaro Linux MATE, Firefox AppImage, probably I'm the only one with that combination.)

Everything is all right now.

Ugh, spell checker! How to turn it off in Vivaldi... maybe I have to update my files about other programs...

This plug was just flakey. 

Should not matter which OS or package installation type you have for your Firefox. The only thing it required was javascript and stuff from like 2015 web era at that.

How do you like Manjaro? I've heard good things about it and tried it way way back when it first came out in a VM but never gave it too much love.

[grymmjack]

@grymmjack -  Plug-ins will never be as good unless made by same caliber of developer as that which they plug-in to.

This reminds me of a saying: "If you want something to be really good, make it yourself!"

Working with forum plugins reminds me of an old saying as well: "Two steps forward, one step back."  

Every time we implement a couple of new things, half of them end up having to be reverted as they just won't work properly without glitching out somewhere, or bugging out something else that we'd installed previously.  Honestly, it truly does seem like that for every two plugins we install (two steps forward), we end up having to remove one of them (and that's the step back).

Who knew programming was so much like a line dance sometimes??

Part of it is the way the plug-ins work together.

Some are just clobbering each other.

The MyBB architecture is really well made, no lie.

Also, considering everyone that's made stuff with it (especially me) was new to MyBB and didn't understand how things worked and just got busy messing with stuff, are we surprised at this outcome? I'm not.

Also also, what fun would it really be if it was just "I want this" then "You got that". The journey is where the "fun" is

[TerryRitchie]

Spacing is not being preserved correctly when posting code using any of the code tags. If you look at the code I just posted here:

https://staging.qb64phoenix.com/showthre...4#pid17014

You can see my REM statements don't line up. They do in my original code however.

[bplus]

Spacing is not being preserved correctly when posting code using any of the code tags. If you look at the code I just posted here:

https://staging.qb64phoenix.com/showthre...4#pid17014

You can see my REM statements don't line up. They do in my original code however.

You are talking about the comments always starting on same column, I assume.
Do you use tabs or something else besides spaces to get that alignment?

[RhoSigma]

Spacing is not being preserved correctly when posting code using any of the code tags. If you look at the code I just posted here:

https://staging.qb64phoenix.com/showthre...4#pid17014

You can see my REM statements don't line up. They do in my original code however.

Hi Terry, indeed this seems to happen with the [ q b ] code tag and as I noticed somtimes it even get worse after editing/updating a post containing such codeboxes, but couldn't find out a cause for that to give @grymmjack a hint where to look for a fix.

However, you know and used already the IDE code export facility in your tutorial. Since v3.8.0 you can also export into a [ q b = e x p o r t ] forum codebox which preserves all spacing and links keywords to the Wiki pages as usual. The only "disadvantage" is that this type of codebox does not have line numbers.

[bplus]

Spacing is not being preserved correctly when posting code using any of the code tags. If you look at the code I just posted here:

https://staging.qb64phoenix.com/showthre...4#pid17014

You can see my REM statements don't line up. They do in my original code however.

Hi Terry, indeed this seems to happen with the [ q b ] code tag and as I noticed somtimes it even get worse after editing/updating a post containing such codeboxes, but couldn't find out a cause for that to give @grymmjack a hint where to look for a fix.

However, you know and used already the IDE code export facility in your tutorial. Since v3.8.0 you can also export into a [ q b = e x p o r t ] forum codebox which preserves all spacing and links keywords to the Wiki pages as usual. The only "disadvantage" is that this type of codebox does not have line numbers.

Ah good an example of qb = export to test!

Code: (Select All)

_Title "test my 3 for 1 function" ' b+ 2023-06-22

For i = 1 To 12

    Print FillNumberStr$(i, "0", 1234), FillNumberStr$(i, " ", 1234), FillNumberStr$(i, "_", 1234)

Next

Print "Result make sure places is greater or equal to longest number to display"

Print "In the 1234 example that would be 4 digits for places"



Function TS$ (nn) '                                        this comment started on column 60

    TS$ = Right$("0000" + LTrim$(Str$(nn)), 4)

End Function

Function TS1$ (nn1) '                                      this comment started on column 60

    TS1$ = Right$("00" + LTrim$(Str$(nn1)), 2)

End Function

Function TS2$ (nn2) '                                      this comment started on column 60

    TS2$ = Right$("000" + LTrim$(Str$(nn2)), 3)

End Function



'  replace above Functions with a generic string filler 2023-06-22

Function FillNumberStr$ (places As Integer, char$, number As Long)

    '                                                      make sure places is >= to longest (in digits)

    '                                                      number to display, char$ might work oddly

    '                                                      with more than 1 alphanumeric.

    FillNumberStr$ = Right$(String$(places, char$) + _Trim$(Str$(number)), places)

End Function

Looks like that worked, all my comments line up on column 60.

[TerryRitchie]

Spacing is not being preserved correctly when posting code using any of the code tags. If you look at the code I just posted here:

https://staging.qb64phoenix.com/showthre...4#pid17014

You can see my REM statements don't line up. They do in my original code however.

You are talking about the comments always starting on same column, I assume.
Do you use tabs or something else besides spaces to get that alignment?

Nope, I never use tabs for spacing. In the DOS days this would cause strange things to happen between editors so I got in the habit of never using them.

---

Spacing is not being preserved correctly when posting code using any of the code tags. If you look at the code I just posted here:

https://staging.qb64phoenix.com/showthre...4#pid17014

You can see my REM statements don't line up. They do in my original code however.

Hi Terry, indeed this seems to happen with the [ q b ] code tag and as I noticed somtimes it even get worse after editing/updating a post containing such codeboxes, but couldn't find out a cause for that to give @grymmjack a hint where to look for a fix.

However, you know and used already the IDE code export facility in your tutorial. Since v3.8.0 you can also export into a [ q b = e x p o r t ] forum codebox which preserves all spacing and links keywords to the Wiki pages as usual. The only "disadvantage" is that this type of codebox does not have line numbers.

It's happening with the standard code tags as well, which never used to happen before.

[TerryRitchie]

Spacing is not being preserved correctly when posting code using any of the code tags. If you look at the code I just posted here:

https://staging.qb64phoenix.com/showthre...4#pid17014

You can see my REM statements don't line up. They do in my original code however.

Hi Terry, indeed this seems to happen with the [ q b ] code tag and as I noticed somtimes it even get worse after editing/updating a post containing such codeboxes, but couldn't find out a cause for that to give @grymmjack a hint where to look for a fix.

However, you know and used already the IDE code export facility in your tutorial. Since v3.8.0 you can also export into a [ q b = e x p o r t ] forum codebox which preserves all spacing and links keywords to the Wiki pages as usual. The only "disadvantage" is that this type of codebox does not have line numbers.

Ah good an example of qb = export to test!

Code: (Select All)

_Title "test my 3 for 1 function" ' b+ 2023-06-22

For i = 1 To 12

    Print FillNumberStr$(i, "0", 1234), FillNumberStr$(i, " ", 1234), FillNumberStr$(i, "_", 1234)

Next

Print "Result make sure places is greater or equal to longest number to display"

Print "In the 1234 example that would be 4 digits for places"



Function TS$ (nn) '                                        this comment started on column 60

    TS$ = Right$("0000" + LTrim$(Str$(nn)), 4)

End Function

Function TS1$ (nn1) '                                      this comment started on column 60

    TS1$ = Right$("00" + LTrim$(Str$(nn1)), 2)

End Function

Function TS2$ (nn2) '                                      this comment started on column 60

    TS2$ = Right$("000" + LTrim$(Str$(nn2)), 3)

End Function



'  replace above Functions with a generic string filler 2023-06-22

Function FillNumberStr$ (places As Integer, char$, number As Long)

    '                                                      make sure places is >= to longest (in digits)

    '                                                      number to display, char$ might work oddly

    '                                                      with more than 1 alphanumeric.

    FillNumberStr$ = Right$(String$(places, char$) + _Trim$(Str$(number)), places)

End Function

Looks like that worked, all my comments line up on column 60.

But there is no syntax highlighting? I like the syntax highlighting.