unable to display extenion in the left windows

Just as the following picture shows:

With the environment Win11 and vscode 1.78.2
And once I click the button "create", there was a error pop out:
"Display Name or Discription can't be empty!".
Seems there is another error, may be it would be helpful to solve the problem I mention before.

I haven't upgraded to Win11, I will borrow my classmates' laptops to fix it in the next few days

I have fixed possible bugs, but I am not sure if I have resolved your issue

I have fixed possible bugs, but I am not sure if I have resolved your issue

Is it possible for me to use the newest version of the extension for test? could you upload it?

I have fixed possible bugs, but I am not sure if I have resolved your issue

Is it possible for me to use the newest version of the extension for test? could you upload it?

I have already uploaded it

I have fixed possible bugs, but I am not sure if I have resolved your issue

Is it possible for me to use the newest version of the extension for test? could you upload it?

I have already uploaded it
Problem exist still though I have been updated to the version 0.1.2.

extensions does not display either.

May be there are some other bugs lead to this problem?

I have fixed possible bugs, but I am not sure if I have resolved your issue

Is it possible for me to use the newest version of the extension for test? could you upload it?

I have already uploaded it
Problem exist still though I have been updated to the version 0.1.2.

extensions does not display either.

May be there are some other bugs lead to this problem?

我又简单改了一下，已经上传完了。还是不行的话，只能以后等我慢慢测试了。实在是没复现出这个bug。

还是不行，总之还是多谢了，目前用另外一个插件也做到了想要的功能

I have fixed possible bugs, but I am not sure if I have resolved your issue

Is it possible for me to use the newest version of the extension for test? could you upload it?

I have already uploaded it
Problem exist still though I have been updated to the version 0.1.2.

extensions does not display either.

May be there are some other bugs lead to this problem?

我又简单改了一下，已经上传完了。还是不行的话，只能以后等我慢慢测试了。实在是没复现出这个bug。

还是不行，总之还是多谢了，目前用另外一个插件也做到了想要的功能

Hi there.
I'm experiencing the same issue - no loading of extensions.  Running in ArchLinux, so it doesn't seem to be platform-related.
2023-07-13 23:06:51.582 [error] TypeError: The "path" argument must be of type string. Received undefined
at new NodeError (node:internal/errors:387:5)
at validateString (node:internal/validators:121:11)
at join (node:path:1166:7)
at new Extension (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.3/out/utils/extension.js:37:61)
at Extension.readFromFile (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.3/out/utils/extension.js:53:34)
at /home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.3/out/panels/controller.js:63:77
at Array.map ()
at getExtensions (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.3/out/panels/controller.js:63:45)
at controller (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.3/out/panels/controller.js:36:13)
at i.value (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.3/out/panels/ExtensionManagerPanel.js:89:78)
at p.w (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:1902)
at p.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:2119)
at l.$onMessage (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:103:27044)
at t.N (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:11199)
at t.M (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:10965)
at t.H (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:10046)
at t.G (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:9261)
at i.value (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:7952)
at p.w (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:1902)
at p.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:2119)
at f.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:76:13931)
at i.value (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:127:30341)
at p.w (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:1902)
at p.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:2119)
at f.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:76:13931)
at MessagePortMain. (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:127:28621)
at MessagePortMain.emit (node:events:513:28)
at MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:367)
Let me know if I can provide anything else from my side that could help solve.  Good looking extension, so I look forward to using it :)

Adding - Above logs were on previous version of VSCode and Simple Extension Manager to test if issue remains.
Updated to latest again, similar error:
023-07-13 23:17:02.697 [error] TypeError: The "path" argument must be of type string. Received undefined
	at new NodeError (node:internal/errors:387:5)
	at validateString (node:internal/validators:121:11)
	at join (node:path:1166:7)
	at new Extension (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.4/out/utils/extension.js:37:61)
	at Extension.readFromFile (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.4/out/utils/extension.js:53:34)
	at /home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.4/out/panels/controller.js:63:77
	at Array.map (<anonymous>)
	at getExtensions (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.4/out/panels/controller.js:63:45)
	at controller (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.4/out/panels/controller.js:36:13)
	at i.value (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.4/out/panels/ExtensionManagerPanel.js:89:78)
	at p.w (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:1902)
	at p.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:2119)
	at l.$onMessage (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:103:27044)
	at t.N (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:11199)
	at t.M (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:10965)
	at t.H (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:10046)
	at t.G (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:9261)
	at i.value (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:7952)
	at p.w (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:1902)
	at p.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:2119)
	at f.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:76:13931)
	at i.value (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:127:30341)
	at p.w (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:1902)
	at p.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:2119)
	at f.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:76:13931)
	at MessagePortMain.<anonymous> (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:127:28621)
	at MessagePortMain.emit (node:events:513:28)
	at MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:367)

Adding - Above logs were on previous version of VSCode and Simple Extension Manager to test if issue remains.
Updated to latest again, similar error:
023-07-13 23:17:02.697 [error] TypeError: The "path" argument must be of type string. Received undefined
	at new NodeError (node:internal/errors:387:5)
	at validateString (node:internal/validators:121:11)
	at join (node:path:1166:7)
	at new Extension (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.4/out/utils/extension.js:37:61)
	at Extension.readFromFile (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.4/out/utils/extension.js:53:34)
	at /home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.4/out/panels/controller.js:63:77
	at Array.map (<anonymous>)
	at getExtensions (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.4/out/panels/controller.js:63:45)
	at controller (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.4/out/panels/controller.js:36:13)
	at i.value (/home/pik/.vscode/extensions/bloodycrown.simple-extension-manager-0.1.4/out/panels/ExtensionManagerPanel.js:89:78)
	at p.w (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:1902)
	at p.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:2119)
	at l.$onMessage (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:103:27044)
	at t.N (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:11199)
	at t.M (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:10965)
	at t.H (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:10046)
	at t.G (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:9261)
	at i.value (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:7952)
	at p.w (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:1902)
	at p.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:2119)
	at f.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:76:13931)
	at i.value (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:127:30341)
	at p.w (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:1902)
	at p.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:2119)
	at f.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:76:13931)
	at MessagePortMain.<anonymous> (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:127:28621)
	at MessagePortMain.emit (node:events:513:28)
	at MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:367)

I have fixed it based on your error log and have updated the plugin. If you still cannot use it after the update, please display the error log. This is very helpful for me to fix the bug, and I would greatly appreciate it.


Forc should automatically build all test projects and their dependencies when running tests.

I don't think this is really a Forc thing so much as it is that the stdlib test harness doesn't have that feature.

https://github.com/FuelLabs/sway/blob/85032fb96c55efa9fbe3ac00eb5b3b0c5c2af051/examples/build-all-examples/src/main.rs#L30-L34


Institution Content - COE

Describe the task

Lynn to implement content updates in DEV environment.
Content updates include business feedback, accessibility (AA+), and B.C. government content standards.

Acceptance Criteria

[ ] Update COE table
[ ] Update COE view
[ ] Update modal view

@astridSABC will create a new ticket once Jeremy is done his content review


[2pt]  Display reserved rockets in My profile - Filters

Render a list of all reserved rockets (use filter()) on the "My profile" page.

@jfoyarzo Implement the Rockets in My Profile


[DOCS] Add requirements for adding libraries that require extra configuration

Description
Currently, there are no specific requirements for updating the documentation when new PRs introduce new libraries that require additional setup steps.
Proposed Solution:
We should update the contributing guidelines to mandate that new PRs introducing new libraries with extra setup requirements must also include relevant documentation for setting up the project.
Screenshots
No response
Additional information
No response
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read and understood the rules in the Contributing Guidelines

Are you willing to work on this issue ?
None

don't worry about this


Consistent US spelling in docs and fix typos

PR Checklist

[x] This comment contains a description of changes (with reason)
[x] Referenced issue is linked: Fixes #740
[ ] If you've fixed a bug or added code that should be tested, add tests! N/A
[x] Documentation in docs is updated
[ ] readthedocs rendering of affected parts visually inspected

Description of changes

Use consistently the American "neighbors" instead of "neighbours"
Changes to documentation focusing on typos.

Technical details

This is an API level change

Additional context

Maintain backwards compatibility, or break ep.pp.knn_impute(..., n_neighbours)?

I love PRs like these. I'd advocate to keep backwards compatibility. It should be easy with kwargs. It's one of the few parameters that people probably use. This should also fix the tutorial CI :)

Something completely different:
https://github.com/theislab/ehrapy/blob/38bd3495d1bd091fd7a731510fdbba5584674bca/ehrapy/tools/feature_ranking/_rank_features_groups.py#L330
This line should be deleted in my opinion. Right?

Something completely different:
https://github.com/theislab/ehrapy/blob/38bd3495d1bd091fd7a731510fdbba5584674bca/ehrapy/tools/feature_ranking/_rank_features_groups.py#L330
This line should be deleted in my opinion. Right?

Yeah I guess so

This should also fix the tutorial CI :)

It wont though if an old ehrapy version is used, and the tutorial uses n_neighbors...
But we're ready to help if someone runs into this :)


GUI players not found

Workflow version
2024.1
Alfred version
5.5 [2257]
macOS version
Sonoma 14.4
Debugger output
[13:26:40.715] STDERR: Play Address[Run Script] Unable to find application named 'com.colliderli.iina'

More details
The issue is related to the script below, which uses the open command to open a media URL with one of several GUI players:
# GUI players
for gui in 'io.mpv' 'com.vitorgalvao.mpvdummy' 'com.colliderli.iina' 'org.videolan.vlc'
do
  if [[ "$(/usr/bin/mdfind kMDItemCFBundleIdentifier = "${gui}")" ]]
  then
    open -na "${gui}" --args "${url}"
    exit 0
  fi
done

I tested the command open -na com.colliderli.iina in Terminal, but it resulted in the same error. It appears that the open command on macOS 14.4 behaves differently.
According to the usage information for open displayed in Terminal on macOS 14.4:

-a: Opens with the specified application.
-b: Opens with the specified application bundle identifier.

To fix this issue, two possible workarounds are suggested:

Change
open -na "${gui}" --args "${url}"
to
open -nb "${gui}" --args "${url}".

Add a variable app_path as follows:

# GUI players
for gui in 'io.mpv' 'com.vitorgalvao.mpvdummy' 'com.colliderli.iina' 'org.videolan.vlc'
do
  app_path=$(/usr/bin/mdfind kMDItemCFBundleIdentifier = "${gui}")
  if [[ "${app_path}" ]]
  then
    open -na "${app_path}" --args "${url}"
    exit 0
  fi
done

Thank you. Fixed and new version has been released.


For multiproject solution with different build target name mapping, cbuild cannot identify build sequence

For NXP RT platform multiproject solution, usually cm7 core project target name is not same with cm4 core project target name, like cm7 flexspi_nor_debug work with cm4 debug. And cm7 doesn't have debug target, cm4 does have flexspi_nor_debug target.
Here is the csolution yml:
solution:
  created-for<EMAIL_ADDRESS>  packs:
  - pack: NXP::MULTICORE
  - pack: NXP::MIMXRT1176_DFP
  - pack: NXP::MIMXRT1170-EVKB_BSP
  - pack: ARM::CMSIS
  target-types:
  - type: armgcc
    compiler: GCC
  - type: iar
    compiler: IAR
  - type: mdk
    compiler: AC6
  output-dirs:
    outdir: "$ProjectDir()$/$TargetType$/$BuildType$"
  build-types:
  - type: flexspi_nor_debug
    context-map:
    - hello_world_cm4.debug
  - type: flexspi_nor_release
    context-map:
    - hello_world_cm4.release
  - type: debug
    context-map:
    - hello_world_cm7.flexspi_nor_debug
  - type: release
    context-map:
    - hello_world_cm7.flexspi_nor_release
  projects:
  - project: cm4/hello_world_cm4.cproject.yml
    not-for-context:
    - ".flexspi_nor_debug+iar"
    - ".flexspi_nor_release+iar"
    - ".flexspi_nor_debug+mdk"
    - ".flexspi_nor_release+mdk"
    - ".flexspi_nor_debug+armgcc"
    - ".flexspi_nor_release+armgcc"
  - project: cm7/hello_world_cm7.cproject.yml
    not-for-context:
    - ".debug+armgcc"
    - ".release+armgcc"
    - ".debug+mdk"
    - ".release+mdk"
    - ".debug+iar"
    - ".release+iar"

When we use cbuild cmd like
cbuild hello_world_multicore.csolution.yml --update-rte -c .flexspi_nor_debug+mdk -O /e/open_CMSIS_ws/11151112

The cbuild will report such issue:
: Could not find incbin file 'core1_image.bin'
        .incbin "core1_image.bin"

The core1_image.bin is the output of cm4 debug. In this case, cbuild doesn't get correct build sequence and it doesn't build cm4 target(not sure whether it is because cm7 has built failure), we expect cm4 to be build firstly, then cm7. The sequence is recorded in the csolution project order.
For platform like lpcxpresso55s69 in which all core project targets are named as "debug", when we run
cbuild hello_world_multicore.csolution.yml --update-rte -c .debug+mdk -O /e/open_CMSIS_ws/11151114

core1 and core0 pojects are build with sequence designated in csolution yml and passed.

@tcsunhao , thanks for reporting the issue you are seeing.
Looking at your command line  you specify the contexts
-c .flexspi_nor_debug+mdk

This means you expect to build the projects
hello_world_cm4.cproject.yml
hello_world_cm7.cproject.yml

However you have explicitly excluded this project for this build-type target-type combination.
 - project: cm4/hello_world_cm4.cproject.yml
    not-for-context:
    - ".flexspi_nor_debug+mdk"

If my understanding of the implementation is correct (@brondani, please comment), the whole context processing on the csolution.yml file level only deals with specified target-types and build-types and does not consider the context-map: nodes.
Only when the actual processing of the cproject file starts, the target-type and build-type get mapped.
Processing the csolution.yml for the above command line results in the request to build,
assuming we are removing the not-for-context: for hello_work_cm4
hello_world_cm4.flexspi_nor_debug+mdk
hello_world_cm7.flexspi_nor_debug+mdk

The processing of hello_world_cm4.cproject.yml will use the mapped build-type debug:
hello_world_cm4.debug+mdk

It seems it is the same example already discussed in https://github.com/Open-CMSIS-Pack/cbuild/issues/99.

Hi @brondani , yes, it is the same example already discussed in https://github.com/Open-CMSIS-Pack/cbuild/issues/99, I don't think we have got expectation. So I want to discuss here again. Now our test team has to open the csolution to analyze to get the mapping between projects, then build with
cbuild hello_world_multicore.csolution.yml --update-rte -c .flexspi_nor_debug+mdk,.debug+mdk -O <output_dir>

We think this mapping analysis shall be done in cbuild side.
Hi @jkrech , we cannot remove not-for-context for cm4 projects because our cm4 projects really doesn't support the listed targets. We expect cbuild can get build sequence from csolution yml and do the build for all projects of the solution. I think it is a common need for all users as well.

These are the required changes. In the csolution.yml there is only build-type debug and release
solution:
  created-for<EMAIL_ADDRESS>  packs:
  - pack: NXP::MULTICORE
  - pack: NXP::MIMXRT1176_DFP
  - pack: NXP::MIMXRT1170-EVK_BSP
  - pack: ARM::CMSIS
  target-types:
  - type: armgcc
    compiler: GCC
  - type: iar
    compiler: IAR
  - type: mdk
    compiler: AC6
  output-dirs:
    outdir: "$ProjectDir()$/$TargetType$/$BuildType$"
  build-types:
#  - type: flexspi_nor_debug
#    context-map:
#    - rpmsg_lite_pingpong_cm4.debug
#  - type: flexspi_nor_release
#    context-map:
#    - rpmsg_lite_pingpong_cm4.release
  - type: debug
    context-map:
    - rpmsg_lite_pingpong_cm7.flexspi_nor_debug
  - type: release
    context-map:
    - rpmsg_lite_pingpong_cm7.flexspi_nor_release
  projects:
  - project: cm4/rpmsg_lite_pingpong_cm4.cproject.yml
 #   not-for-context:
 #   - ".flexspi_nor_debug+iar"
 #   - ".flexspi_nor_release+iar"
 #   - ".flexspi_nor_debug+mdk"
 #   - ".flexspi_nor_release+mdk"
 #   - ".flexspi_nor_debug+armgcc"
 #   - ".flexspi_nor_release+armgcc"
  - project: cm7/rpmsg_lite_pingpong_cm7.cproject.yml
 #   not-for-context:
 #   - ".debug+armgcc"
 #   - ".release+armgcc"
 #   - ".debug+mdk"
 #   - ".release+mdk"
 #   - ".debug+iar"
 #   - ".release+iar"

As a result of the context-map while processing the rpmsg_lite_pingpong_cm7.cproject.yml file the build-type .debug is replaced by .flexspi_nor_debug when processing for-context conditions.
When using access sequences it is probably best to only specify the project and no build-type:
"-I$OutDir(rpmsg_lite_pingpong_cm4)$"

Invocation of cbuild:
  cbuild rpmsg_lite_pingpong.csolution.yml -c .release

will first build cm4 release for all toolchains followed by cm7 without the need for the user to understand which contexts belong to each other because that is specified through the context-map.

Thank you very much @jkrech for this detailed illustration. We have updated our multiproject solution for RT platforms and test environment. Now all works.


Dotnet Program

Problem encountered on https://dotnet.microsoft.com/en-us/learn/aspnet/hello-world-tutorial/install
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
Windows 10, it says the program was installed but doesn't open when attempted. I ran a repair on the program and still not working, any help is appriciated.

What program are you trying to run?

I didn't understand that i needed to run the command for dotnet in an IDE,
i figured it out. Thanks
On Fri, Jul 21, 2023 at 6:05 PM Maira Wenzel @.***>
wrote:

What program are you trying to run?
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/8639#issuecomment-1646281272, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BBNXSRKPHYYBBEA5HASOMPTXRL4LZANCNFSM6AAAAAA2TLNZLE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok, so I'll close the issue then.


Create Pause Menu

Create a pause menu. If someone exits the game or an interuption occurs, the pause menu will appear. It will contain a resume button.

I wiIl create the pause menu.

The pause menu will also contain an exit button.

You might want to check out Scene2D for creating the menus, http://www.gamefromscratch.com/page/LibGDX-Tutorial-series.aspx part 9 (1-4). Basically, use the menu as the "scene" and the buttons as "actors". This is optional, but might be handy.

This seems very helpful. I will take a closer look at it.

I have implemented a basic version of the pause menu using similar code from the main menu. The problem is that it does not restart from where you left off.

I can't help if you don't provide any information about your problem

The pause screen starts a new GameScreen when the program resumes. Therefore, a completely new game starts and the old one is erased. I have been trying to find ways to resume the current GameScreen but so far it has only caused the game to crash. I have been trying to run
several screens concurrently and then using game.GameScreen.show(); but as I previously stated, it crashes the game.

Check this link out. https://stackoverflow.com/questions/11466496/libgdx-game-how-to-display-pause-screen-when-user-click-on-pause-icon. Remember that when pressing the "back" button on android, the bottom left button, the game exits. Starting the game from that state should start the game from beginning. Pressing the home button (bottom-center) however, puts the application in the background. Android calls the "pause()" callback in that case, which is where you handle the pausing.


edge support

using a custom bundle until https://github.com/webrtc/adapter/pull/136 gets merged.

+1

I'll be merging this and testing out on our side soon. Lots of stuff on my backlog and Edge is lower... Thanks for doing all of this.