Issues with new plugins/extension from megabundle

[makeshyft]

Hello Stam,

I just did a session with Mark T, and he showed me the stack running on his M1 stack, and it is surprisingly slower than my super average windows machine with a less than average gpu. I'm really not sure why that is the case. Maybe I am using something that is significantly slower on mac than windows. I'm going to work on testing and optimizing the stack better for mac.

Though a couple of the things you mentioned seem quite unnatural and abnormal to what the experience should be.

A video would still help.

Thanks again,

Tom

Hi Tom,
As a sidenote i wondered if there was an update to appStarterPack so decided to re-download. However this website is slightly painful:
- there are no downloads in account > downloads section
- in my previous 'purchases' ($0.00 as obtained with megabundle) there is a download link to download my previous 'purchase' but it states i have reached the download limit
- i created a new purchase (again, $0.00 with the megabundle code) and started a download, but this stalled and failed - a problem i had previously with your demo versions ('connection with server is lost' or some such). Actually as yet i have not been able to successfully download the mac demo.
- if i try to re-download the 'new purchase' i am again told i have reached the download limit for the 'purchase'.

I can certainly re-create yet another purchase as with my megabundle code this is free, but what happens if someone has purchased this directly?
Shouldn't the 'purchased' product appear in account > downloads?

Hello Stam,

All you have to do is drop me an email and we can work out whatever issues there are with your account.
This is not the support forum for the AppStarterStack.
https://www.appstarterstack.com/contact/

Thanks,

Tom

[makeshyft]

Stam,

It seems as if you are under the impression that the AppStarterStack was somehow supposed to be made for your likes and preferences.
It has features that you may need/like or not need and not like .. such as the minimizing of the application instead of closing.
Some people might like the option on keeping the application minimized.
All you have to do is delete the lines of code that you do not want running.
To be honest I don't really understand your attitude and expectations.
How could I possibly know what you will find annoying?

Thanks,

Tom

[makeshyft]

Also, to change how the stack windows rearrange themselves, you can change the code in the "IDERearrange" handler of the stack "Start Here".

NOTHING in the AppStarterStack is hard coded, and if there are things you want to change, go ahead, that is the point of it all, to change the stack and its code to suite your needs.

[makeshyft]

As far as the crash you demoed, its because the "ContentGroups" custom property of that card seems to have an empty line in it, or a name that does not match an existing group. The file you were supplied with does not produce this error.

Stam, I think its important for you to set some time aside for learning, its not a step that you can skip.

Once you do that, you will be able to get somewhere. If you are too busy to learn, then you are too busy to use the AppStarterStack.

Please message me from the site if you have issues that you'd like help with. Posting them here is not the best place.

Thanks,

Tom

[stam]

As far as the crash you demoed, its because the "ContentGroups" custom property of that card seems to have an empty line in it, or a name that does not match an existing group. The file you were supplied with does not produce this error.

Stam, I think its important for you to set some time aside for learning, its not a step that you can skip.

Once you do that, you will be able to get somewhere. If you are too busy to learn, then you are too busy to use the AppStarterStack.

Please message me from the site if you have issues that you'd like help with. Posting them here is not the best place.

Thanks,

Tom

Tom

Thank you for your multiple answers. I appreciate you do not use this as the support forum, but I did not purchase this from you directly, i purchased the LiveCode Megabundle so had posed the question in the LiveCode forum - apologies if you consider this inappropriate.

You requested further details and I provided them. At no point did you link to a support forum to take my questions to or any other way to report back. Then you use 4 consecutive forum posts to tell me i'm wrong and seem upset i haven't used your support mechanism.

I'm not sure I appreciate the tone either.
All reported issues were seen using the stack AppStarterStack-V099-LCMegaBundle-Final.livecode, unmodified.
i did not try to use appStarterStack, but immediately hit these issues putting this stack into browse mode.
Or perhaps you are suggesting that this stack should not even be viewed if "learning" hasn't taken place?

If a developer offers me a solution that inadvertently (and unnecessarily) changes my own IDE environment, moving windows so high that their titlebars are off-screen and changing the backdrop colour, this is not my issue, it's a bug.
Admittedly, although i could reproduce the crash I reported every time, this now seems very intermittent. Essentially the 'greyed out' group (posing as a button) can be clicked occasionally, leading to the crash. I cannot say I understand why.
As to the 'account' question, i think it's clear what i'm asking: Once a purchaser has checked out the product and downloaded it, there is no obvious way i could see to download it again, you have to repeat the checkout process. I may be wrong, hence the question. Still not sure what the answer is...

So thank you for your tip on "setting time aside to learn" - but my "learning" has nothing to do with the reported issues. I did not try to use appStarterStack, just view the attached stack, as provided.

I will not trouble you any further with this, and this discussion can end here as I can't see this being fruitful.
If there are any burning issues i'll use your web form to contact you.

[makeshyft]

Hello Stam,

I'm sorry you are having troubles.
Regarding the error you were getting, I was unable to reproduce it from a the mega-bundle download.
But was able to reproduce it based on how I know that error to happen.
I will check it again.

I attempted to respond to each issue you expressed, I'm sorry if I missed one, please let me know which one.

A few of the issues, such as a feature you didn't like, or a color you didn't like.
Those are solved by working with the stack and removing the code you want running.
Which is how the stack is customized to your needs.

My statement regarding learning may sound pretty straight forward, but that really is the answer to getting comfortable with the stack and making small tweaks to make it work the way you want. I am also offering training sessions after the sale ends, so maybe you can find the time to attend those, or watch them.


The download limit is set to 3 for your products, so oyu should be able to do that by going to MY ACCOUNT > DOWNLOADS
I checked your account and it says that your first order has 2 downloads and the second has 3.
That file will not be updated, all updates will be posted to github.
The first update is scheduled for the first week of september, and will be code only.

Let me know what of your issues I missed.

Thanks,

Tom

[makeshyft]

A video would still help.

Hi Tom, further to my previous posts, I've tested again on my older MacBook Pro - 2012 15' MBP (2.3 GHz quad core i7 with 16 Gb RAM) running latest version of MacOS Big Sur and latest LC IDE.

Machine speed is seems to be an issue an issue although i've not had any kind of slowdowns running other apps, and my own LC apps run admirably on this machine. You can see in the video below that on hovering over the Engine Info button flickers the entire stack with a grey overlay, not visible really on my faster mac but definitely visible on a slower mac:

Video: https://share.cleanshot.com/rFJgE8

Screenshot:
flicker.jpg

HTH
Stam

Stam,

I think its likely you are having graphics driver issues.
There is no code that would make the content of the stack disappear when you hover over a button.
And you are also saying that this does not happen on both your machines, which implies that the problem is elsewhere and not with the stack.
Also, just to make sure, the stack was built using 9.8 stable. Is that the version you have?

[stam]

By “9.8 stable” I presume you mean “ 9.6.8”. Yes this is what I am running as explicitly stated in my early posts, alongside machine specs.

“Graphics driver issues” is a nonsense statement on macOS.
And yours is the only stack/app that has these issues (note that the machine is capable of running 3D networked games, with a frame rate of > 50 FPS with high graphics quality, so it’s no slouch).

If you ask me, I think the issue is with graphics objects manipulation in LC on Mac which behaves differently. Evidently you are changing the background colour of graphics objected in mouseEnter/Leave. Unless you “Lock Screen” this is what happens in LC on Mac, and the slower the Mac the obvious the issue.

But frankly I feel disinclined to look into this further.
If I do decide to look further in this product and encounter issues I will use your web form as stated.

[makeshyft]

By “9.8 stable” I presume you mean “ 9.6.8”. Yes this is what I am running as explicitly stated in my early posts, alongside machine specs.

“Graphics driver issues” is a nonsense statement on macOS.
And yours is the only stack/app that has these issues (note that the machine is capable of running 3D networked games, with a frame rate of > 50 FPS with high graphics quality, so it’s no slouch).

If you ask me, I think the issue is with graphics objects manipulation in LC on Mac which behaves differently. Evidently you are changing the background colour of graphics objected in mouseEnter/Leave. Unless you “Lock Screen” this is what happens in LC on Mac, and the slower the Mac the obvious the issue.

But frankly I feel disinclined to look into this further.
If I do decide to look further in this product and encounter issues I will use your web form as stated.

Yes I did mean 9.6.8

I checked the behavior script to see if the screen is locked before the objects are changed and indeed it does.
line 562 and 593 of the mouseEnter handler. (of the behavior script of navigation items)

But the mouseLeave handler does not have a lock screen, perhaps adding that would solve this strange issue, I will include it in the next update to the code.

Okey Doke.