I am using createStackNavigator. I have three screens: A, B, and C
Screen B is used twice during my transition. I use this notation:
B(1): The first time we transit to screen B with some parameters
B(2): The second time we transit to screen B with different parameters
Consider this transition:
A --> B(1) --> C --> B(2)
Current behavior:
When I transit from screen A to B(1), B(1) to C, each time the new screen appears with an animation from right to left. But when I transit from C to B(2), the new screen appears from left to right. (issue 1)
When I am on B(2) and use navigation.goBack(), I see A (but I want to see C of course)
(issue 2)
Expected Behaviour:
when I transit from C to B(2), the new screen must appear from right to left (Like previous transitions)
When I am on B(2) and use navigation.goBack(), I must see C
System:
OS: macOS 10.15.3
CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU # 2.70GHz
Memory: 246.99 MB / 8.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.13.1 - ~/.nvm/versions/node/v12.13.1/bin/node
npm: 6.12.1 - ~/.nvm/versions/node/v12.13.1/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 28, 29
Build Tools: 28.0.3, 29.0.2
System Images: android-28 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.5 AI-191.8026.42.35.5977832
Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-36.0.1.tar.gz => 0.61.4
"react-navigation": "^4.3.7",
"react-navigation-stack": "^1.10.3",
To fix "when I transit from C to B(2), the new screen must appear from right to left (Like previous transitions)" in screen C use this code to navigate :
// this pushes B into the stack insted of navigating to B
() => navigation.push('B')
This "When I am on B(2) and use navigation.goBack(), I must see C" will be already fixed because the stack order is correct using push insted of navigate.
So your stack preview screen will be C.
Related
Describe the bug
in p-steps completed and incompleted steps should have different styles just to differentiate between them. .It was possbile with primeng9 version with ui-steps-incomplete and ui-steps-complete classes. but after migrating to 11 these classes have been removed. is there any alternate way we could do this?
Environment
Windows 10
Angular version: Angular 11
PrimeNG version: 11.4.5
node: 16.10
Reproducer
No response
Angular version
11
PrimeNG version
11.4.5
Build / Runtime
Angular CLI App
Language
ALL
Node version (for AoT issues node --version)
16.10
Browser(s)
No response
Steps to reproduce the behavior
currentbehaviour
go to p-steps and try to click next in steps . so that it shifts from step1 to step2, step2 to step3 etc
Expected behavior
if the user completes step1 and goes to steps2
step1(that is already completed should have some colors ie color1, background1 )
active one should have color2, background2
step3 ie next steps (incomplete one's) should have color3, background3
expected
When attempting to use Expo (SDK 43) in managed mode on an iPad Air 4th Gen (OS 15.0.2) with expo-three, expo-gl and a <GLView> with a model containing a SkinnedMesh and transparent textures, I receive the following warning:
Warning: THREE.WebGLRenderer: EXT_color_buffer_float extension not supported.
This is further confirmed with requesting the list of available extensions:
const ext = glContext.getExtension("EXT_color_buffer_float");
const availableExtensions = glContext.getSupportedExtensions();
...
Supported render extensions: APPLE_clip_distance,APPLE_color_buffer_packed_float,APPLE_copy_texture_levels,
APPLE_rgb_422,APPLE_texture_format_BGRA8888,EXT_color_buffer_half_float,EXT_debug_label,EXT_debug_marker,
EXT_pvrtc_sRGB,EXT_read_format_bgra,EXT_separate_shader_objects,EXT_shader_framebuffer_fetch,
EXT_shader_texture_lod,EXT_shadow_samplers,EXT_texture_filter_anisotropic,IMG_read_format,
IMG_texture_compression_pvrtc,KHR_texture_compression_astc_ldr,OES_standard_derivatives,
OES_texture_float_linear,OES_texture_half_float_linear,WEBGL_compressed_texture_astc,
WEBGL_compressed_texture_etc,WEBGL_compressed_texture_pvrtc
Required extension EXT_color_buffer_float: NOT AVAILABLE!
...
But what is confusing is that the render capabilities indicate the WebGL2 is available:
console.log(`Render Capabilities: ${JSON.stringify(renderer.capabilities)}`);
...
Render Capabilities: {"isWebGL2":true,"drawBuffers":true,"precision":"highp","logarithmicDepthBuffer":false,
"maxTextures":16,"maxVertexTextures":16,"maxTextureSize":16384,"maxCubemapSize":16384,
"maxAttributes":16,"maxVertexUniforms":512,"maxVaryings":15,"maxFragmentUniforms":224,
"vertexTextures":true,"floatFragmentTextures":true,"floatVertexTextures":true,"maxSamples":4}
and webglreport.com in Safari indicates that WebGL2 is supported and that the EXT_color_buffer_float is available. In fact, the extension list differs from the webglreport.
Versions
expo sdk: 43
expo-gl: 11.0.3
expo-gl-cpp: 11.0.1
expo-three: 6.0.1
react: 17.0.1
react-native: 0.64.2
three: 0.133.1
Question
How can I enable actual/complete WebGL2 support with the complete extension set as reported by webglreport with react-native on ios15?
I am trying to build a browser extension using clojurescript and re-agent (wrapper around react). The code is very simple (complete source and repro steps here), mostly copied from a re-agent example:
(ns clext2.core
(:require [reagent.core :as r]))
(defn timer-component []
(let [seconds-elapsed (r/atom 0)]
(fn []
(js/setTimeout #(do (println "timeout") (swap! seconds-elapsed inc)) 1000)
[:div "Seconds Elapsed: " #seconds-elapsed])))
(let [app (js/document.createElement "div")
_ (js/document.body.appendChild app)]
(r/render [timer-component] app))
I compiled this with the :simple optimization flag, copied the generated js into the example code published by Mozilla: https://github.com/cljsjs/packages/wiki/Creating-Packages, and loaded the extension on chromium and firefox.
Observations
When I test with figwheel locally, the counter renders in both chromium and firefox.
When I navigate to a real page (not using figwheel):
With firefox, the counter loads but does not increment (timeout is printed once)
With chrome, the counter loads and increments (timeout is printed every second)
Expected behavior
I would expect the counter to get visibly increment with firefox and it does not.
Browser Versions
Chromium (71.0.3578.98 (Official Build) Manjaro Linux (64-bit))
Firefox (64.0 for manjaro).
My question
I am not sure how to debug this further, what can I try next?
You are conflating the view (visual aspect) with the events (timer stuff). You should keep then separate. Please see the re-frame docs.
I am connecting to a SQL server database in R using the RODBC package and making multiple calls to the database, doing something with the result, writing the result to disk and removing all variables. I then call gc() and close the channel before starting the next iteration. This is roughly shown below.
for(i in 1:1000){
ch <- odbcConnect("some dsn")
result = sqlQuery(ch, 'SELECT * from table where some_condition = i')
#some processing here...
saveRDS(result, 'result.rdata')
# this should remove all object in memory
rm(result)
gc()
odbcClose(ch)
}
My problem is that as the loop progresses, the amount of memory being used by R gets larger and larger (as revelaed in the windows Resouce Monitor), despite the total size of the objects in the global environment not increasing. Eventually, I use up all of the memory available on my machine (16gb, Windows 7, 64 bit) and the process crashes.
Why is this happenning?
How can I force R to free up the memory without restarting R?
Things I have tried that did not work:
multiple calls to gc() as suggested here https://stackoverflow.com/a/1467334/366502.
changing the buffsize, rows_at_time and believeNRows arguments in sqlQuery()
sessionInfo()
R version 3.2.0 (2015-04-16)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 7 x64 (build 7601) Service Pack 1
locale:
[1] LC_COLLATE=English_United Kingdom.1252 LC_CTYPE=English_United Kingdom.1252 LC_MONETARY=English_United Kingdom.1252 LC_NUMERIC=C LC_TIME=English_United Kingdom.1252
attached base packages:
[1] stats graphics grDevices utils datasets methods base
other attached packages:
[1] data.table_1.9.4 DBI_0.3.1 rsqlserver_1.0 rClr_0.7-4 text_0.0.0.9000 stringr_1.0.0 plyr_1.8.3 RODBC_1.3-11 rvest_0.2.0 tomr_0.0.0.9000
loaded via a namespace (and not attached):
[1] Rcpp_0.12.0 lattice_0.20-31 XML_3.98-1.2 slam_0.1-32 grid_3.2.0 chron_2.3-47 R6_2.1.1 magrittr_1.5 httr_1.0.0 stringi_0.5-5 reshape2_1.4.1 NLP_0.1-8 Matrix_1.2-1 tools_3.2.0
[15] parallel_3.2.0 tm_0.6-2
Built Raspberry Pi 2 linux distro including Qt5.4 + QtWebKit + QML plugin using Yocto on fido branch See tutorial
Testing with the following QML script
root#raspberrypi2:~# more webkit.qml
import QtWebKit 3.0
WebView {
url: "http://www.nokia.com"
preferredWidth: 490
preferredHeight: 400
scale: 0.5
smooth: false
}
When running this script I am getting the following error:
root#raspberrypi2:~# /usr/bin/qt5/qmlscene --platform eglfs webkit.qml
Unable to query physical screen size, defaulting to 100 dpi.
To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_HEIGHT (in millimeters).
QQmlPropertyCache: QQuickItem has FastProperty class info, but has not installed property accessors
Aborted
Any pointers?
I had the same problem. The solution was to add the line
import QtQuick 2.0
to the QML file.