Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
PNML Petri Net Editor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
DiNeROS
DiNeROS 1
PNML Petri Net Editor
Commits
0d8a1a89
Commit
0d8a1a89
authored
4 months ago
by
tj
Browse files
Options
Downloads
Patches
Plain Diff
adding local changes before going home
parent
5be5d222
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
TaskAndTimeTimJahn.txt
+48
-0
48 additions, 0 deletions
TaskAndTimeTimJahn.txt
with
48 additions
and
0 deletions
TaskAndTimeTimJahn.txt
+
48
−
0
View file @
0d8a1a89
...
@@ -305,3 +305,51 @@ java.lang.ClassCastException: class org.pnml.emf.ptnet.impl.PageImpl cannot be c
...
@@ -305,3 +305,51 @@ java.lang.ClassCastException: class org.pnml.emf.ptnet.impl.PageImpl cannot be c
at org.eclipse.glsp.server.internal.actions.DefaultActionDispatcher.handleNextAction(DefaultActionDispatcher.java:163)
at org.eclipse.glsp.server.internal.actions.DefaultActionDispatcher.handleNextAction(DefaultActionDispatcher.java:163)
at org.eclipse.glsp.server.internal.actions.DefaultActionDispatcher.runThread(DefaultActionDispatcher.java:149)
at org.eclipse.glsp.server.internal.actions.DefaultActionDispatcher.runThread(DefaultActionDispatcher.java:149)
at java.base/java.lang.Thread.run(Thread.java:1583)
at java.base/java.lang.Thread.run(Thread.java:1583)
chatGPT:
To ensure that Sprotty elements (such as nodes, edges, etc.) are always in the foreground,
you would generally need to modify their layer or z-index in the Sprotty framework,
which relies on SVG (Scalable Vector Graphics) elements.
Here’s what you can do:
1. **Set the SVG z-index:**
You can explicitly set a higher `z-index` for the elements you want to be in the foreground.
In Sprotty, elements are typically rendered in layers based on their order in the SVG document.
By assigning the desired elements a higher `z-index`,
they will be rendered on top of other elements.
In the `SModelElement` (or whatever your model element type is),
ensure the `zIndex` attribute is set for the foreground elements:
```typescript
const foregroundElement = {
id: "elementId",
type: "type",
zIndex: 1000 // Higher value to push it to the foreground
};
```
2. **Ensure correct layer ordering in the rendering code:**
If you're directly controlling the layer order in the rendering code,
make sure you render the foreground elements last, after other elements.
3. **Layering in styles:**
If you're using styles to control the appearance,
you can target elements using CSS and set `z-index` directly.
For example:
```css
.foregroundElement {
z-index: 1000;
}
```
4. **Using Sprotty's `zIndex` in component code:**
If you're working with Sprotty’s specific components,
make sure that the foreground elements are being added to a
layer or group that has the highest stacking context.
This ensures they appear on top of other graphical elements.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment