-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set negative draw priority for Building Markers #733
base: master
Are you sure you want to change the base?
Changes from 2 commits
d1caacb
4ec5f8e
885e50e
c1a6c60
9547328
2297b56
3ea5c51
1f379c1
6d7e35c
1d0e8bb
cf0644e
fe71ba1
7b4df37
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||
---|---|---|---|---|---|---|---|---|
|
@@ -61,6 +61,8 @@ if (_set) then { | |||||||
_marker setMarkerDir getDir _object; | ||||||||
_object setVariable [QGVAR(marker), _marker, true]; | ||||||||
|
||||||||
[QEGVAR(common,setMarkerDrawPriority), [_marker, -1], _marker] call CBA_fnc_globalEventJIP; | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Interestingly, CBA_fnc_removeGlobalEventJIP can be told to wait for the object (in this case the marker) to be deleted before actually proceeding with deleting the JIP order, so this should work, adding some inherent sleep by
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Very cool indeed. It would probably need to be There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe, I dunno; just interpreted this line. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||||||||
|
||||||||
// Delete marker when the object is deleted | ||||||||
private _eventID = _object addEventHandler ["Deleted", { | ||||||||
params ["_object"]; | ||||||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to handle removing the JIP event if the marker is deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should building markers be removable for other reasons than building deletion?
Do building markers remain global or should local changes be permitted?
If not, I imagine it's possible to replace the removed marker by detecting when a marker has been deleted with this EH:
If building markers should be removable, I guess the EH linked above still can be used, but it would be a bit more tricky: What if
deleteMarkerLocal
is used on building markers? Should the marker be replaced, so that you force people to usedeleteMarker
instead, or should the marker be editable on each client individually, as in permit different marker settings (existence, visibility, size, direction, etc)?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice one 3ea5c51
I don't think any mod can be so protective of its stuff.
What use case is there for building markers showing differently between clients?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that a mod shouldn't be that overprotective. As for the use case of building markers showing differently on clients, I don't really know, I'm not a mission maker. I was mostly thinking of how badly the marker system could/would break if you started messing with markers on a per client basis.