I did everything I usually do, and I even added eveything to the same group to test to a value. And for SOME reason they are still overlapping strangely even with differences in Y being plain to see.
So just to verify, increasing sort by a value higher is behind, and lower is infront?
decreasing opposite?
For some reason two active types are having conflict, and it makes no sense since Im pretty sure layer object just chooses all of actives as one group regardless? Ha.. I dont know whats wrong.
I've had the layer object act weird a few times. Try removing and adding it again.
heres the mfa (hope no one steals it :/) I cant figure out why this is happening on line 214 i tried a bunch of stuff to get it to work
layerbroke_targetfinder.mfa
ill let the first person who can tlel me EXACTLY why this doesnt work steal my design up to this point and use it as a base for their own game lolz I dont even care anymore, im just confused why this does not work
in eventline 224, just before sorting,
set current layer to layer1
(layer object --> layers ---> by index ---> set current layer)
also, don't know if this is intended,
but some objects have hotspots in different positions than others
Y position is taken at hot spot, so you may want to "normalize" them
(or you can set value K to YBottom)
woah, because of you i went back to look at the problem and I suddenly found the library tool bar with tons of widgets and stuff. Is that all free to use in commercial products?
anyway, I still dont un derstand man, is therre a reasn the layer object cant operate just fine with the moving/target objects? I thought each layer object automatically self targeted its own layer and just sorted everything in that layer based on values or Y. Very confused about this friend. Any help is appreciated in explaining this to me. Clickteam is very difficult for me to understand sometimes. (and yeah how embarrising i missed one of the objects i had normalized before but i always keep mixing up ACTION SPOT with HOT SPOT =-/
Yeah you have to set current layer to make sure sorting affects objects in that layer.
From help file:
Set Current Layer
Sets the Current Layer, used in the Sort and Reverse actions.
Get Current Layer
Retrieves the index of the current layer. The Current Layer is the one selected by the Set Current Layer action. The Sort, Move, Bring To actions of the Layer object affect only the objects of the Current Layer.
Don't know which one is chosen by default when there are ore than one, possibly the higher index?
(would be easy to test and know for sure, anyway)
You can obviously sort multiple layers with multiple conditions
first question (is library free?),
I would guess this answer for older version (MMF) applies:
http://community.clickteam.com/threads/66658-Library-pack-graphics?highlight=Library%20commercial
Posting Permissions
Reply With Quote