You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This should be relatively easy to do with a simple rewrite of the zIndex system.
Currently when an element is selected by a guest, it calls UpdateElementZIndex on the server. This loops through all Elements getting the min and max zIndex. From there, we increment the recently selected element by the max+1. If the min and max exceed a ceiling threshold, the zIndex numbers are reset (this is to avoid an integer overflow for really really old/high traffic modules).
We could simply set a value: 900001, for example, that the min/max loop ignores, however I think this feature should allow multiple elements to be "Always On Top", which would require those elements to have their own layering within their high 900001 value. So probably what I'll do is make a range (of a few thousand) 900001-999999 that are excluded from the min/max loop and then still allow incrementing within that "Always On Top" range. Will also need a reset once that range hits the max as well.
Good luck future chippy!
The text was updated successfully, but these errors were encountered:
This should be relatively easy to do with a simple rewrite of the zIndex system.
Currently when an element is selected by a guest, it calls
UpdateElementZIndex
on the server. This loops through all Elements getting the min and max zIndex. From there, we increment the recently selected element by the max+1. If the min and max exceed a ceiling threshold, the zIndex numbers are reset (this is to avoid an integer overflow for really really old/high traffic modules).We could simply set a value: 900001, for example, that the min/max loop ignores, however I think this feature should allow multiple elements to be "Always On Top", which would require those elements to have their own layering within their high 900001 value. So probably what I'll do is make a range (of a few thousand) 900001-999999 that are excluded from the min/max loop and then still allow incrementing within that "Always On Top" range. Will also need a reset once that range hits the max as well.
Good luck future chippy!
The text was updated successfully, but these errors were encountered: